Closed domenic closed 4 years ago
Prefix it with "Hard", i.e. HardDate, HardTime, HardDateTime.
Just because dates are hard.
Another way to think about Local
types is that they are adequate for applications with a local (as opposed to global) userbase. JavaScript is ubiquitous, this mnemonic seems sensible for "native" applications.
This has been solved. We’re nit prefixing, but namespacing in the Temporal global.
@pipobscure Hope the proposal repo could be updated soon. 😃
Currently the "civil time" types are prefixed with
Plain
. This is a bit confusing and unclear to me, so I thought it would be worthwhile to start a thread exploring alternatives.To be clear, this kind of bikeshedding is not a big issue or blocker, and hopefully will not be too frustrating for the proposal authors. But I think it's a discussion worth having.
Some alternatives:
Plain
Civil
Local
(I think this is what they were originally called, and I agree it's probably bad)Floating
?Unzoned
?