Material-ui: v1.0.0-alpha.21 - different API problems
I know this is alpha, but will the full version have all of these breaking changes?
Almost every component has been changed.
SelectField even doesn't exist anymore...
My application uses the Select field a lot, so if it's not here anymore, what should I use to replace it? Do I have to build my own?
mnemanja
All 3 comments
The simple answer is, yes, the API will be different. This is to be expected because the approach to styling has been dramatically improved and is very different. Along the way, tremendous effort has been put forth to deliver a streamlined, consistent API while adhering to Material Design standards. The cost of doing so is the introduction of breaking changes.
Sure, there are components that are not implemented yet, but this is an alpha release. Regarding the SelectField specifically, there have been previous attempts at porting it and there is an existing issue. If you have an immediate need and you're able to help, that would be very much in the spirit of OSS! 馃槃
If you embark on porting your application and gather information that would be useful for others undertaking this process, I am 馃挴 sure that @oliviertassinari and @rosskevin (and everyone else) would appreciate a documentation PR.
Please refer to the roadmap for more information about v1.
kgregory
on 6 Jul 2017
Thanks for the thorough answer @kgregory.
Regarding existing use of alpha + legacy Select, you would need to use both concurrently (which is what I currently do) similar to this comment.
Any help on porting Select is appreciated.
rosskevin
on 6 Jul 2017
Thanks, guys!
Hopefully, I'll have some free time in the near future.
Keep up with the good work.
Cheers :)
mnemanja
on 7 Jul 2017
Related issues
zabojad
路
3Comments
mb-copart
路
3Comments
mattmiddlesworth
路
3Comments
finaiized
路
3Comments
anthony-dandrea
路
3Comments
Most helpful comment
The simple answer is, yes, the API will be different. This is to be expected because the approach to styling has been dramatically improved and is very different. Along the way, tremendous effort has been put forth to deliver a streamlined, consistent API while adhering to Material Design standards. The cost of doing so is the introduction of breaking changes.
Sure, there are components that are not implemented yet, but this is an alpha release. Regarding the SelectField specifically, there have been previous attempts at porting it and there is an existing issue. If you have an immediate need and you're able to help, that would be very much in the spirit of OSS! 馃槃
If you embark on porting your application and gather information that would be useful for others undertaking this process, I am 馃挴 sure that @oliviertassinari and @rosskevin (and everyone else) would appreciate a documentation PR.
Please refer to the roadmap for more information about v1.