Shane F. Carr
Shane F. Carr
Concretely, I envision DateTimeFormat using the following separate, orthogonal keys, which covers all formatting except for time zone (which I want to leave to a separate discussion): **Display Names** 1....
There are still some open questions in my mind about how exactly to provision data across calendar systems, but that question is being tracked in #355.
Shane to implement this along with #355.
Blocked on #409 like #355
Also migrate the date data provider structs to have real lifetime parameters.
I'm going to punt this to Q2 because I want to wait for the work on availableFormats to stabilize. I don't see a need to introduce merge conflicts.
Re-opening to address the following remaining issues: 1. Skeletons should be separated from patterns 2. Time symbols should be separated from date symbols
I'm hoping that @gregtatum's design work today puts us on a path to eventually resolve these questions about what should be in the data keys. We should have a deeper...
This should be one of the last things to do in 1.0 after DTF has stabilized. We should do this before 1.0 because it impacts data file stability.
Make sure to look at the data representation of the glue pattern and make changes if necessary for future-proofing. See #1131