Marc Mintel
5397309103
Some checks failed
Build & Deploy / 🔍 Prepare (push) Successful in 20s
Build & Deploy / 🧪 QA (push) Failing after 34s
Build & Deploy / 🏗️ Build (push) Has started running
Build & Deploy / 🚀 Deploy (push) Has been cancelled
Build & Deploy / 🧪 Smoke Test (push) Has been cancelled
Build & Deploy / ⚡ Lighthouse (push) Has been cancelled
Build & Deploy / 🔔 Notify (push) Has been cancelled
12 lines
690 B
Plaintext
12 lines
690 B
Plaintext
import { type Formats as IntlFormats } from 'intl-messageformat';
|
|
import type Formats from './Formats.js';
|
|
import type TimeZone from './TimeZone.js';
|
|
/**
|
|
* `intl-messageformat` uses separate keys for `date` and `time`, but there's
|
|
* only one native API: `Intl.DateTimeFormat`. Additionally you might want to
|
|
* include both a time and a date in a value, therefore the separation doesn't
|
|
* seem so useful. We offer a single `dateTime` namespace instead, but we have
|
|
* to convert the format before `intl-messageformat` can be used.
|
|
*/
|
|
export default function convertFormatsToIntlMessageFormat(globalFormats?: Formats, inlineFormats?: Formats, timeZone?: TimeZone): Partial<IntlFormats>;
|