You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's a revert. I have made the unwise call of adding the InputClasses property in an unrelated refactorization pull-request #8942. It was not taking the input classes property into account. It was a breaking change and not needed.
33
+
-[core] Reduce bundle size by 2kB gzipped (#9129) @oliviertassinari
34
+
We have removed some jss plugins from the default bundle:
-[jss-compose](https://github.com/cssinjs/jss-compose) (426 B)
37
+
-[jss-extend](https://github.com/cssinjs/jss-extend) (702 B)
38
+
-[jss-template](https://github.com/cssinjs/jss-template) (330 B)
32
39
33
40
It's a revert.
34
41
I have made the unwise call of adding the InputClasses property in an unrelated refactorization pull-request #8942.
@@ -1613,7 +1620,7 @@ You now have two way to customize absolutely all the CSS injected by Material-UI
1613
1620
Either the instance level with the `classes` property or the class level with the
1614
1621
`overrides` theme property.
1615
1622
1616
-
To [learn more about it](https://material-ui-next.com/customization/overrides), have a look at the documentation. Also, these options are automatically [documented](http://0.0.0.0:3000/component-api/button#classes).
1623
+
To learn more about it, have a look at the documentation.
Copy file name to clipboardExpand all lines: ROADMAP.md
+19-47Lines changed: 19 additions & 47 deletions
Original file line number
Diff line number
Diff line change
@@ -2,29 +2,28 @@
2
2
3
3
The roadmap is a living document, and it is likely that priorities will change, but the list below should give some indication of our plans for the next major release, and for the future.
4
4
5
-
⚠️ New features based on `v0.19.x` have low priority and will most likely not be reviewed nor merged. We want to focus on bug fixes.
6
-
7
5
## Version 1 (published on NPM under the `next` tag)
8
6
9
-
Version 1 release is going to be huge ✨.
10
-
We host a temporary [documentation site](https://material-ui-next.com) for the pre-releases.
7
+
Releasing stable v1 is our top priority. It's going to be huge ✨.
8
+
We are just at the beginning, we hope to make it:
9
+
- the **simplest** React UI library available for new Front-End developers to start with.
10
+
-**very customizable** so highly UI demanding production applications can save time building on top of it.
11
11
12
12
Material-UI was started [3 years ago](https://github.com/mui-org/material-ui/commit/28b768913b75752ecf9b6bb32766e27c241dbc46).
13
13
The ecosystem has evolved a lot since then, we have also learned a lot.
14
14
[@nathanmarks](https://github.com/nathanmarks/) started an ambitious task, rebuilding Material-UI from the **ground-up**
15
15
taking advantage of this knowledge to address long-standing issues.
16
16
Expect various **breaking changes**.
17
17
18
-
The core team is now helping him in the [v1-beta](https://github.com/mui-org/material-ui/tree/v1-beta) branch.
18
+
The core team has been dedicated to the rewrite effort for one and a half years.
19
19
If you are interested in following our progress or if you want to help us reach that goal faster, you can have a look at the following milestones:
The `v1-beta` branch has become more mature, so we think that it's a good time to communicate more on this effort.
26
-
We have a lot of people opening PRs and getting them closed, this is not a good thing.
27
-
This Q&A tries to answer some of your questions.
26
+
The v1-beta version has matured, so we think that it's time to communicate more on this effort. The following Q&A is an attempt at answering some of your questions.
28
27
29
28
### Summarizing, what are our main problems with CSS?
30
29
@@ -58,50 +57,21 @@ Computing the inline-style at each render with no caching isn't really efficient
58
57
59
58
Yes, it does. You can have a look at [this presentation](https://github.com/oliviertassinari/a-journey-toward-better-style) for more details.
60
59
61
-
## What does it mean to migrate a component? Should we discuss each one of them first?
62
-
63
-
Migrating a component to the `v1-beta` branch isn't just a style migration.
64
-
We think that it's our best opportunity to clear the API and improve the implementation of the components.
65
-
@nathanmarks ended up fixing a lot of long standing issues in the process.
66
-
67
-
Yes, it would much better to discuss an action plan for each of them that would save us considerable time compared to blindly following a wrong path.
68
-
We should answer the following questions:
69
-
- What will the API look like?
70
-
- What trade-offs are we going to make?
71
-
- What features will be implemented?
72
-
73
-
That conversation could start on one of the following [issues](https://github.com/mui-org/material-ui/issues?q=is%3Aissue+is%3Aopen+label%3ARefactoring+label%3Anext).
74
-
75
-
### How do I know if a component still needs to be migrated `v1-beta`?
76
-
77
-
We have [some open issues](https://github.com/mui-org/material-ui/issues?q=is%3Aopen+is%3Aissue+label%3ARefactoring+label%3Av1) to **coordinate** the work toward the `v1.0.0` release.
78
-
79
-
### How do I start migrating components to the `v1-beta` branch?
80
-
81
-
Once we agree on the migration plan you're going to have to get your hands dirty.
82
-
That's really up to you. At least, you going to have to:
83
-
- clone the `v1-beta` branch
84
-
- install the npm dependencies
85
-
- play with the documentation site
86
-
- write some documentation
87
-
- write some tests (unit, integration, visual)
88
-
89
-
### When do we intend to release `v1`?
60
+
### When do we intend to release stable v1?
90
61
91
-
We don't have an ETA for the release of the `v1`, however, we are going to try to follow this plan:
62
+
We don't have an ETA for the release of the `v1`, however, we are going to try to follow this plan and hope for a Q1-Q2 2018 release:
92
63
93
64
1.~~We completely address the styling issue before moving from *alpha* to [*beta*](https://github.com/mui-org/material-ui/milestone/22).~~
94
65
2.~~We publish our first beta releases.~~
95
-
3. We fix the last API inconsistencies (as we can make breaking changes without having to worry much).
96
-
4. We merge the beta branch into master
66
+
3. We merge the v1-beta branch into master
97
67
5. We publish our first pre-releases, if all goes well, we move to the next step.
98
68
6. We publish v1 🎉
99
69
100
-
At that point, some features and components from the v0.x will be missing in the v1.
70
+
At that point, some features and components from Material-UI v0.x will be missing in the v1.
101
71
So, what about them?
102
72
- First, both versions can be used at the same time, people can progressively migrate, one component at the time.
103
73
- Then, **with the help of the community** and over time, we will support more and more components.
104
-
- We would rather **support few use-cases very well and allow people to build on top of it**than many poorly.
74
+
- We would rather **support few use-cases very well** and allow people to build on top of it**than many poorly**.
105
75
106
76
### Have we ever considered using the best libraries for each piece of functionality and provide only a wrapper for the UI?
107
77
@@ -117,8 +87,10 @@ We think that it should be done the other way around, i.e. providing a low-level
117
87
118
88
On the other hand, using a smart date library for the DatePicker / TimePicker would probably be much better as date management is tricky and not a core business.
119
89
120
-
## Future
90
+
## After stable v1
121
91
122
-
- Add missing components, and missing features from current ones
123
-
-[[#7721](https://github.com/mui-org/material-ui/issues/7721)] Preact support
124
-
-[[#593](https://github.com/mui-org/material-ui/issues/593)] Support React Native
92
+
-**Theming**. We will invest in the theming solution. We would love to see **non Material Design UI** built with Material-UI. [@oliviertassinari](https://github.com/oliviertassinari/) is working on a proof of concept.
93
+
-**Type checking**. We need to improve TypeScript and Flow coverage of the library.
94
+
-**Bundle size**. We need the library to be as small as possible. We already monitor the bundle size with size-limit. We need to think of the solutions. For instance, supporting preact can help.
95
+
-**Performance**. We can't optimize something we can't measure. We don't have any CI performance benchmark. We will need to build one and start investigating bottlenecks.
96
+
-**Learning materials**. The documentation is equally as important as the quality of the implementation. We could be authoring a [learning tutorial](https://learnnextjs.com/) like Next.js is doing, or some [egghead.io](https://egghead.io/) courses.
0 commit comments