Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Version Packages #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Version Packages #1

wants to merge 1 commit into from

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Feb 19, 2020 •
edited
Loading

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@arch-ui/[email protected]

Major Changes

  • e9a0de2c #2927 Thanks @Vultraz! - Upgraded to date-fns 2.x. This version uses Unicode tokens for its formatting strings. A conversion table is available here.

    This change only affects the CalendarDay and DateTime fields' format config option.

    The following script utilizes the @date-fns/upgrade package and can be used to convert old formatting strings:

    const { convertTokens } = require('@date-fns/upgrade/v2');

console.table(
  [
    // Add date-dns 1.x formatting strings here.
  ].map(str => ({
    v1: str,
    v2: convertTokens(str).replace(/'/g, ''),
  }))
);

    Do note this converts symbols to standalone style as opposed to formatted style which may not always be desired. For example, DD/MM/YYYY would be converted to dd/LL/yyyy instead of dd/MM/yyyy. See here for more information on which you should use.

Patch Changes

  • 59ed6310 #2930 Thanks @Vultraz! - Fixed many usability issues with the CalendarDay field:

    • Fixed field not functioning as a proper controlled component in the Create popout.
    • Fixed field initially displaying "Invalid Date" before defaulting to 1970-01-01.
    • Filter input no longer defaults to the current date. This was bugged; submitting the form with no changes would match nothing.
    • Filter input now falls back to no value when given an invalid date. Previously, it was falling back to 1970-01-01.
    • Fixed filter input not initially displaying the current value when in edit mode (it was displaying the current date).
    • Fixed filter input not being initially focused.
    • Fixed filter input not being submitted properly if focus wasn't lost first.

    Updated chrono-node dependency to 1.4.6.

@keystonejs/[email protected]

Major Changes

  • e9a0de2c #2927 Thanks @Vultraz! - Upgraded to date-fns 2.x. This version uses Unicode tokens for its formatting strings. A conversion table is available here.

    This change only affects the CalendarDay and DateTime fields' format config option.

    The following script utilizes the @date-fns/upgrade package and can be used to convert old formatting strings:

    const { convertTokens } = require('@date-fns/upgrade/v2');

console.table(
  [
    // Add date-dns 1.x formatting strings here.
  ].map(str => ({
    v1: str,
    v2: convertTokens(str).replace(/'/g, ''),
  }))
);

    Do note this converts symbols to standalone style as opposed to formatted style which may not always be desired. For example, DD/MM/YYYY would be converted to dd/LL/yyyy instead of dd/MM/yyyy. See here for more information on which you should use.

Patch Changes

@keystonejs/[email protected]

Major Changes

  • e9a0de2c #2927 Thanks @Vultraz! - Upgraded to date-fns 2.x. This version uses Unicode tokens for its formatting strings. A conversion table is available here.

    This change only affects the CalendarDay and DateTime fields' format config option.

    The following script utilizes the @date-fns/upgrade package and can be used to convert old formatting strings:

    const { convertTokens } = require('@date-fns/upgrade/v2');

console.table(
  [
    // Add date-dns 1.x formatting strings here.
  ].map(str => ({
    v1: str,
    v2: convertTokens(str).replace(/'/g, ''),
  }))
);

    Do note this converts symbols to standalone style as opposed to formatted style which may not always be desired. For example, DD/MM/YYYY would be converted to dd/LL/yyyy instead of dd/MM/yyyy. See here for more information on which you should use.

Patch Changes

  • 54931d75 #2923 Thanks @timleslie! - Updated documentation for the CalendarDay field type.

  • 59ed6310 #2930 Thanks @Vultraz! - Fixed many usability issues with the CalendarDay field:

    • Fixed field not functioning as a proper controlled component in the Create popout.
    • Fixed field initially displaying "Invalid Date" before defaulting to 1970-01-01.
    • Filter input no longer defaults to the current date. This was bugged; submitting the form with no changes would match nothing.
    • Filter input now falls back to no value when given an invalid date. Previously, it was falling back to 1970-01-01.
    • Fixed filter input not initially displaying the current value when in edit mode (it was displaying the current date).
    • Fixed filter input not being initially focused.
    • Fixed filter input not being submitted properly if focus wasn't lost first.

    Updated chrono-node dependency to 1.4.6.

  • Updated dependencies [e9a0de2c, 3b0f4137, 15c57317, 59ed6310, 2709a6b5]:

@keystonejs/[email protected]

Major Changes

  • e9a0de2c #2927 Thanks @Vultraz! - Upgraded to date-fns 2.x. This version uses Unicode tokens for its formatting strings. A conversion table is available here.

    This change only affects the CalendarDay and DateTime fields' format config option.

    The following script utilizes the @date-fns/upgrade package and can be used to convert old formatting strings:

    const { convertTokens } = require('@date-fns/upgrade/v2');

console.table(
  [
    // Add date-dns 1.x formatting strings here.
  ].map(str => ({
    v1: str,
    v2: convertTokens(str).replace(/'/g, ''),
  }))
);

    Do note this converts symbols to standalone style as opposed to formatted style which may not always be desired. For example, DD/MM/YYYY would be converted to dd/LL/yyyy instead of dd/MM/yyyy. See here for more information on which you should use.

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Major Changes

  • e9a0de2c #2927 Thanks @Vultraz! - Upgraded to date-fns 2.x. This version uses Unicode tokens for its formatting strings. A conversion table is available here.

    This change only affects the CalendarDay and DateTime fields' format config option.

    The following script utilizes the @date-fns/upgrade package and can be used to convert old formatting strings:

    const { convertTokens } = require('@date-fns/upgrade/v2');

console.table(
  [
    // Add date-dns 1.x formatting strings here.
  ].map(str => ({
    v1: str,
    v2: convertTokens(str).replace(/'/g, ''),
  }))
);

    Do note this converts symbols to standalone style as opposed to formatted style which may not always be desired. For example, DD/MM/YYYY would be converted to dd/LL/yyyy instead of dd/MM/yyyy. See here for more information on which you should use.

Patch Changes

@keystonejs/[email protected]

Major Changes

  • e9a0de2c #2927 Thanks @Vultraz! - Upgraded to date-fns 2.x. This version uses Unicode tokens for its formatting strings. A conversion table is available here.

    This change only affects the CalendarDay and DateTime fields' format config option.

    The following script utilizes the @date-fns/upgrade package and can be used to convert old formatting strings:

    const { convertTokens } = require('@date-fns/upgrade/v2');

console.table(
  [
    // Add date-dns 1.x formatting strings here.
  ].map(str => ({
    v1: str,
    v2: convertTokens(str).replace(/'/g, ''),
  }))
);

    Do note this converts symbols to standalone style as opposed to formatted style which may not always be desired. For example, DD/MM/YYYY would be converted to dd/LL/yyyy instead of dd/MM/yyyy. See here for more information on which you should use.

Patch Changes

@keystonejs/[email protected]

Major Changes

  • e9a0de2c #2927 Thanks @Vultraz! - Upgraded to date-fns 2.x. This version uses Unicode tokens for its formatting strings. A conversion table is available here.

    This change only affects the CalendarDay and DateTime fields' format config option.

    The following script utilizes the @date-fns/upgrade package and can be used to convert old formatting strings:

    const { convertTokens } = require('@date-fns/upgrade/v2');

console.table(
  [
    // Add date-dns 1.x formatting strings here.
  ].map(str => ({
    v1: str,
    v2: convertTokens(str).replace(/'/g, ''),
  }))
);

    Do note this converts symbols to standalone style as opposed to formatted style which may not always be desired. For example, DD/MM/YYYY would be converted to dd/LL/yyyy instead of dd/MM/yyyy. See here for more information on which you should use.

Patch Changes

@keystonejs/[email protected]

Major Changes

  • e9a0de2c #2927 Thanks @Vultraz! - Upgraded to date-fns 2.x. This version uses Unicode tokens for its formatting strings. A conversion table is available here.

    This change only affects the CalendarDay and DateTime fields' format config option.

    The following script utilizes the @date-fns/upgrade package and can be used to convert old formatting strings:

    const { convertTokens } = require('@date-fns/upgrade/v2');

console.table(
  [
    // Add date-dns 1.x formatting strings here.
  ].map(str => ({
    v1: str,
    v2: convertTokens(str).replace(/'/g, ''),
  }))
);

    Do note this converts symbols to standalone style as opposed to formatted style which may not always be desired. For example, DD/MM/YYYY would be converted to dd/LL/yyyy instead of dd/MM/yyyy. See here for more information on which you should use.

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

@keystonejs/[email protected]

Patch Changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants