issues
search
tc39
/
proposal-stable-formatting
A TC-39 proposal to bring stable Intl-inspired formatting options to ECMAScript
12
stars
2
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Choose between general and specific solutions
#17
eemeli
opened
9 months ago
1
Advance to Stage 1
#16
eemeli
closed
1 year ago
0
TC-39 -> TC39
#15
nicolo-ribaudo
closed
1 year ago
0
Add a second possible solution
#14
eemeli
closed
1 year ago
1
Specify behavior for APIs that take natural-language input as opposed to producing natural-language output
#13
hsivonen
opened
1 year ago
6
Consider a pure ECMA262 approach
#12
FrankYFTang
closed
1 year ago
17
Add link to June 2023 presentation
#11
sffc
closed
1 year ago
0
Refactor as "Stable Formatting"
#10
eemeli
closed
1 year ago
3
How to handle the`calendar` option in this proposal's Intl.DTF?
#9
justingrant
opened
1 year ago
0
How should Intl.DTF `timeZoneName` option be formatted in this proposal?
#8
justingrant
opened
1 year ago
1
How should Intl.DTF formats in this proposal's locale relate to Temporal objects' `toStriing()` output?
#7
justingrant
opened
1 year ago
0
Is "root locale" a good term for this locale?
#6
justingrant
closed
1 year ago
0
Should `null` be accepted in place of the string ID for this locale?
#5
justingrant
closed
1 year ago
3
Should subtags be accepted?
#4
justingrant
opened
1 year ago
1
Backwards compatibility implications of using an existing ID like `'und'` or `'zxx'` for this proposal
#3
justingrant
closed
1 year ago
3
Need to define which option values are supported in Intl methods with null locale
#2
justingrant
opened
1 year ago
3
Consider `zxx` instead of `und`
#1
eemeli
closed
1 year ago
0