Remove fmt:
prefix for date formats
#260
Comments
|
@pwalsh hmmm - i am not sure this is in contraints - basic parsing and checking constraints seems to me different things and though we could use
i.e. we introduce |
@rgrp i see. It might be a bit confusing to have both @roll @vitorbaptista @akariv @amercader any thoughts? |
Using Or we need other word I suppose to replace
|
We had the same issue with numeric values. |
But it will lead to |
@roll yes - you could call it |
IMO, if I understand this issue correctly, it would be nice to "format": "pattern",
"pattern": "%Y" |
@Hypercubed good suggestion. @pwalsh I'd like to make a choice here soon. I think I'm a definite -1 (or, at least, -0) on overloading This basically leaves us with this as the proposal:
We could rename What do people think? AsideWorth thinking about use cases. In my experience with core datasets the major use cases were being able to handle plain year, and year month (i.e.
This is something of an aside and should perhaps be another issue ... |
Re the aside: I would say that quarter / month / year are actually On Tue, 9 Aug 2016 at 11:45 Rufus Pollock notifications@github.com wrote:
|
In terms of naming, we're dealing with printf format strings, so would Re: the aside and @akariv's comment, I think that issue is now in #105 Not really the place for this question, but what was the rationale for |
Re your second question - because not everyone uses it to separate On Tue, Sep 27, 2016, 16:06 James McKinney notifications@github.com wrote:
|
What groups is it separating?
|
@rgrp you are assigned here. I think we need to fix this. Do you want to do a PR, or shall we discuss further? |
I added it to the spec as a way to handle date formatting... but it is pretty ugly and does not feel right. We can probably use
constraints.pattern
to achieve the same, and possibly document some patterns for common date formats.The text was updated successfully, but these errors were encountered: