@limetech/lime-elements 40.22.0 → 40.24.0

package/dist/collection/components/date-picker/date-formatter.js

@@ -7,6 +7,150 @@ import "moment/locale/nl";
 import "moment/locale/sv";
 import moment from "moment/moment";
 import { getPrimarySubtag } from "../../util/language";
+// Literals first, so an `l` inside `[...]` is not expanded. Then longest
+// first, since alternation takes the first match, not the longest.
+const LONG_DATE_FORMAT_TOKENS = /\[[^\][]*\]|LTS|LLLL|LLL|LL|LT|L|lts|llll|lll|ll|lt|l/g;
+// Literals, tokens (runs of one repeated letter) and separators.
+const FORMAT_PARTS = /\[[^\][]*\]|([a-zA-Z])\1*|[^a-zA-Z[]+/g;
+// Tokens moment parses leniently as one or two digits.
+const ONE_OR_TWO_DIGIT_TOKENS = /^([MDHhkmsWw])\1?$/;
+// Includes the narrow no-break space `Intl` puts before AM/PM.
+const WHITESPACE = /\s+/g;
+// ` - ` or `, ` between a date and a time. Separators inside a date, such
+// as `-` in `YYYY-MM-DD`, must still be typed as in the format.
+const DATE_TIME_JOINER = / ?, ?| - /g;
+const TIME_SEPARATOR = /([Hhk]{1,2}|m{1,2})([:.])(?=m{1,2}|s{1,2})/g;
+// Such as `[w]` in `[w] W GGGG`.
+const WEEK_PREFIX = /^\[[^\][]*\]\s*(?=[Ww])/;
+/**
+ * Expands localized tokens, e.g. `L` to `MM/DD/YYYY` for `en`.
+ * @param format - the moment format to expand, e.g. `L` or `L - LT`
+ * @param locale - the moment locale to expand it for
+ */
+function expandLongDateFormatTokens(format, locale) {
+    if (!format) {
+        return format;
+    }
+    const localeData = moment.localeData(locale);
+    return format.replaceAll(LONG_DATE_FORMAT_TOKENS, (token) => {
+        if (token.startsWith('[')) {
+            return token;
+        }
+        return (localeData.longDateFormat(token) ||
+            token);
+    });
+}
+/**
+ * Accepts fewer digits than the format has, e.g. `1/24/20` for
+ * `MM/DD/YYYY`, but rejects text that leaves part of the format unmatched.
+ * Moment's lenient mode alone accepts "01" as a complete date.
+ *
+ * Times and weeks are accepted in more forms than their format, e.g.
+ * `15.30` for `HH:mm` and `v. 4 26` for `[w] W GGGG`.
+ * @param date - the raw text to parse
+ * @param format - the moment format to parse it against
+ * @param locale - the moment locale to parse it in
+ */
+export function parseComplete(date, format, locale) {
+    const text = normalizeSeparators(date);
+    const expandedFormat = normalizeSeparators(expandLongDateFormatTokens(format, locale));
+    for (const candidate of getTimeSeparatorVariants(expandedFormat)) {
+        const parsed = parseLeniently(text, candidate, locale);
+        if (parsed) {
+            return parsed;
+        }
+    }
+    return null;
+}
+function parseLeniently(date, format, locale) {
+    const [weekText, weekFormat] = dropWeekPrefix(date, format);
+    const text = pivotWeekYears(weekText, weekFormat);
+    const parsed = moment(text, weekFormat, locale, false);
+    if (!parsed.isValid()) {
+        return null;
+    }
+    const flags = parsed.parsingFlags();
+    if (flags.charsLeftOver > 0 ||
+        flags.unusedTokens.length > 0 ||
+        hasAmbiguousYear(text, weekFormat)) {
+        return null;
+    }
+    return parsed.toDate();
+}
+// Applied to both the text and the format, so they stay aligned.
+function normalizeSeparators(text) {
+    return text
+        .trim()
+        .replaceAll(WHITESPACE, ' ')
+        .replaceAll(DATE_TIME_JOINER, ' ');
+}
+function getTimeSeparatorVariants(format) {
+    const swapped = format.replaceAll(TIME_SEPARATOR, (_, part, separator) => part + (separator === ':' ? '.' : ':'));
+    return swapped === format ? [format] : [format, swapped];
+}
+// Accepts any prefix, e.g. `v.`, `w` or none, for `[w] W GGGG`.
+function dropWeekPrefix(date, format) {
+    if (!WEEK_PREFIX.test(format)) {
+        return [date, format];
+    }
+    return [date.replace(/^\D*/, ''), format.replace(WEEK_PREFIX, '')];
+}
+// Moment pivots a 2-digit `YYYY`, e.g. `26` to 2026, but not `GGGG`.
+function pivotWeekYears(date, format) {
+    const twoDigitWeekYears = findYears(date, format).filter(({ token, start, end }) => token === 'GGGG' && end - start === 2);
+    return twoDigitWeekYears.reduceRight((text, { start, end }) => text.slice(0, start) +
+        moment.parseTwoDigitYear(text.slice(start, end)) +
+        text.slice(end), date);
+}
+// Lenient parsing reads a half-typed year such as "1/24/2" as year 2.
+function hasAmbiguousYear(date, format) {
+    return findYears(date, format).some(({ start, end }) => {
+        const digitCount = end - start;
+        return digitCount !== 2 && digitCount !== 4;
+    });
+}
+function findYears(date, format) {
+    const formatParts = format.match(FORMAT_PARTS) || [];
+    const inputPattern = formatParts.map(formatPartToPattern).join('');
+    const match = new RegExp(`^${inputPattern}$`, 'd').exec(date);
+    if (!match) {
+        return [];
+    }
+    return formatParts.filter(isYearToken).map((token, index) => {
+        const [start, end] = match.indices[index + 1];
+        return { token: token, start: start, end: end };
+    });
+}
+function isYearToken(part) {
+    return part === 'YYYY' || part === 'GGGG';
+}
+/**
+ * Literals and separators are optional, since lenient parsing skips them
+ * when they are not typed, e.g. `01242026` for `MM/DD/YYYY`.
+ * @param part - a literal, token or separator of the format
+ */
+function formatPartToPattern(part) {
+    if (part.startsWith('[')) {
+        return optional(part.slice(1, -1));
+    }
+    if (isYearToken(part)) {
+        return String.raw `(\d{1,4})`;
+    }
+    if (ONE_OR_TWO_DIGIT_TOKENS.test(part)) {
+        return String.raw `\d{1,2}`;
+    }
+    if (/^[a-zA-Z]+$/.test(part)) {
+        return '.+?';
+    }
+    // Moment matches each separator character on its own.
+    return [...part].map(optional).join('');
+}
+function optional(text) {
+    return `(?:${escapeRegExp(text)})?`;
+}
+function escapeRegExp(text) {
+    return text.replaceAll(/[.*+?^${}()|[\]\\]/g, String.raw `\$&`);
+}
 export class DateFormatter {
     constructor(language = 'en') {
         this.language = language;
@@ -19,7 +163,9 @@ export class DateFormatter {
     }
     parseDate(date, dateFormat) {
         if (date) {
-            return moment(date, dateFormat).toDate();
+            // Importing the moment locales changes moment's global default
+            // locale, so tokens like `L` must be parsed with ours.
+            return parseComplete(date, dateFormat, this.getLanguage());
         }
         return null;
     }

package/dist/collection/components/date-picker/date-picker.css

@@ -1,3 +1,102 @@
+@charset "UTF-8";
+/**
+* Note! This file is forwarded via `src/style/exports.scss`
+* and exposed to consumers through the root `index.scss`.
+*
+* Consumers import it using:
+* `@use '@limetech/lime-elements' as lime-elements;`
+*
+* Legacy import paths (`dist/scss/mixins`) are maintained
+* for backward compatibility via copy rules in the Stencil config.
+*/
+/**
+* Neutralizes the user-agent styles that browsers apply to `<button>` elements
+* (their default background, border, padding, font, etc.), without stripping
+* the useful defaults that `all: unset;` would also remove
+* (such as `display`, `cursor`, and focus behavior).
+*
+* Prefer this mixin over `all: unset;` on `<button>` elements, then layer
+* the styling you want on top — often one of the `is-*-clickable` mixins.
+*/
+/**
+* This can be used on a trigger element that opens a dropdown menu or a popover.
+*/
+/**
+ * This mixin will mask out the content that is close to
+ * the edges of a scrollable area.
+ * - If the scrollable content has `overflow-y`, use `vertically`
+ * as an argument for `$direction`.
+ - If the scrollable content has `overflow-x`, use `horizontally`
+ * as an argument for `$direction`.
+ *
+ * For the visual effect to work smoothly, we need to make sure that
+ * the size of the fade-out edge effect is the same as the
+ * internal paddings of the scrollable area. Otherwise, content of a
+ * scrollable area that does not have a padding will fade out before
+ * any scrolling has been done.
+ * This is why this mixin already adds paddings, which automatically
+ * default to the size of the fade-out effect.
+ * This size defaults to `1rem`, but to override the size use
+ * `--limel-top-edge-fade-height` & `--limel-bottom-edge-fade-height`
+ * when `vertically` argument is set, and use
+ * `--limel-left-edge-fade-width` & `--limel-right-edge-fade-width`
+ * when `horizontally` argument is set.
+ * Of course you can also programmatically increase and decrease the
+ * size of these variables for each edge, based on the amount of
+ * scrolling that has been done by the user. In this case, make sure
+ * to add a custom padding where the mixin is used, to override
+ * the paddings that are automatically added by the mixin in the
+ * compiled CSS code.
+ */
+/**
+* This mixin will add an animated underline to the bottom of an `a` elements.
+* Note that you may need to add `all: unset;` –depending on your use case–
+* before using this mixin.
+*/
+/**
+* This mixin creates a cross-browser font stack.
+* - `sans-serif` can be used for the UI of the components.
+* - `monospace` can be used for code.
+*
+* ⚠️ If we change the font stacks, we need to update
+* 1. the consumer documentation in `README.md`, and
+* 2. the CSS variables of `--kompendium-example-font-family`
+* in the `<style>` tag of `index.html`.
+*/
+/**
+* This mixin is a hack, using old CSS syntax
+* to enable you to truncate a piece of text,
+* after a certain number of lines.
+*/
+/**
+* This mixin will add a chessboard background pattern,
+* typically used to visualize transparency.
+*/
+/**
+* Make a container resizable by the user.
+* This is used in the documentations and examples
+* of some components, to demonstrate how the component
+* behaves in a resizable container.
+*/
+/**
+ * Drag to reorder mixins
+ */
+/**
+ * The breakpoints below are used to create responsive designs
+ * in Lime's products. Therefore, they are here to get distributed
+ * to all components in other private repos, which rely on this `mixins`
+ * file, to create consistent styles.
+ *
+ * :::important
+ * In very rare cases you should used media queries!
+ * Nowadays, there are many better ways of achieving responsive design
+ * without media queries. For example, using CSS Grid, Flexbox, and their features.
+ * :::
+ */
+/**
+  * Media query mixins for responsive design based on screen width.
+  * Note that these mixins do not detect the device type!
+  */
 /**
  * @prop --dropdown-z-index: z-index of the dropdown menu.
  */
@@ -8,4 +107,17 @@
 limel-input-field[disabled],
 limel-input-field[readonly] {
   pointer-events: none;
+}
+
+.error-message {
+  position: absolute;
+  width: 0;
+  height: 0;
+  margin: -1px;
+  padding: 0;
+  border: 0;
+  overflow: hidden;
+  clip: rect(0, 0, 0, 0);
+  clip-path: inset(50%);
+  white-space: nowrap;
 }