Make Date Pickers Locale-Aware
Description
Environment
Potential Workaround
relates to
Checklist
hideTestRail: Results
Activity
Charlotte Whitt July 3, 2017 at 5:00 PM
Manually tested in http://folio-testing.aws.indexdata.com/ in Chrome, Settings:
@folio/organization 2.0.1-SNAPSHOT.43 depends on:
configuration 1.0 (0.0.9 available) which is as required but present only in an incompatible version - in orange highlight in the About page.
The Date picker is tested for all the different settings for locale rendering dates etc, in Settings > Organization > 'Language and localization'.
Expected:
The date is consequently changed to the date format defined as locale in Settings > Organization > 'Language and localization' - not just in the user detail page, but all through out the system where dates are displayed.
Actually:
1. All looks good in the User Details pane - for all language and localization settings (Eng_US, Eng_GB, Danish, German, and Hungarian)
2. When using scan (check out item to a patron), then the loan date is returned in English_US date format, also when the locale-aware is set to 'Language and localization' different from English_US.
Will close the issue (story), and file a bug.
John Coburn June 19, 2017 at 1:38 PM
Datepickers should work as expected now... no modification necessary. Datefields in the User Edit form should automatically be displaying the same format as displayed in the User Details pane since both are now using the same data from Stripes Context.
Cate Boerema June 19, 2017 at 10:26 AM
Hi guys. I see this is marked In Review. When this is pushed to FOLIO demo-test, do we expect things to work per the scenarios in the user story or is there more work that needs to be done to make use of the changed component?
John Coburn June 14, 2017 at 3:38 PMEdited
Alright. Changes pushed to github: https://github.com/folio-org/stripes-components/commit/032877875a0f32a1098c18696effef068fe676da#diff-bed8556c15184e1b2ba7390eb0e468de
Will go out in 0.15.0
John Coburn June 14, 2017 at 1:58 PM
Thanks Mike! putting off closing this to incorporate exactly that sort of change.
Purpose: Modify date pickers so that the expected input format matches the display format determined by selected locale
Scenarios
Scenario
Given the selected locale maps to date format A (for example, MM/DD/YYYY)
When the ghost text in a date field is displayed
Then, the ghost text should display in format A (in this case, as MM/DD/YYYY)
Scenario
Given the selected locale maps to date format A
When the selected date is displayed in a date field
Then, it should display as format A
Scenario
Given the selected locale maps to date format A
When a date is manually entered into a date field
Then, it should be assume the date is entered in format A and processed accordingly (for save and validation, for example)