Closed robertbastian closed 4 weeks ago
Overlaps with #611. I like this solution, but I also know @sffc had some opinions. Does this sound good?
I like this, though there's another option which is to store this as some form of metadata that the renderer can use, potentially to group things into regions, or use colons, or something else.
This is a low hanging fruit that doesn't require annotating all of ICU4X. Metadata can be built on top of it, but that's considerably more work. The current state is really not good.
Oh 100% we should do the easy thing first
I'm good with this, although I still think the better solution is to just name parameters less ambiguously.
Ok, I'm on this when I have some free time
I like this, though there's another option which is to store this as some form of metadata that the renderer can use, potentially to group things into regions, or use colons, or something else.
Mockup of a good UI for this with <fieldset>
Instead of flattening recursive parameters, like
year
,month
,day
if the argument is aDate
, qualify them:date:month
. Argument names are usually written in the context of a type, so when that is missing they are hard to interpret (e.g.name
for the locale argument).Single-argument names can be omitted, i.e.
locale:name
can just belocale
.