-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.15.0 #2109
Comments
Also, there are quite a few other issues tagged with the 0.15.0 milestone not listed above: https://github.com/callemall/material-ui/issues?q=is%3Aopen+is%3Aissue+milestone%3A%220.15.0+Release%22 Would it make sense to have a dedicated branch for 0.15.0 to allow easy release of 0.14.x releases with segregation of breaking changes targeted for 0.15.0? |
@oliviertassinari Shouldn't by standard Monday be 0? @mbrookes I'm no expert on the standard. Is defaulting to 1 (yet starting from Saturday) against the standard? |
@alitaheri I'm not sure to follow your point. We have |
What I mean is, if by standard the start of the week is Monday, then it's more convenient to start COUNTING from Monday too. in other words it will be like: |
That makes sens 👍. |
I thought the same, which is why I raised the question of the default in the PR, since changing the numbering in a future release could have more impact than just changing the default. However, Date.prototype.getDay() has Sunday=0, so at least it's consistent with that. |
Let's move the conversation here #2980. |
I have a list of task in mind for the next breaking change release.
Top priority
menu
component as it's deprecated sincev0.14.0
and no longer used in the source codefirstDayOfWeek
from0
to1
. [DatePicker] Change the behavior of firstDayOfWeek to follow ISO #2980labelPosition
for theFlatButton
andRaisedButton
. It should follow thelabelPosition
used in theSwitch section
.Nice to have
valueLink
as it's going to be deprecated by react [valueLink] React is deprecating the usage #2880warning
instead of our home made checkThe text was updated successfully, but these errors were encountered: