我应该等待material-ui v1还是现在可以使用预发行版? [英] Should I wait for material-ui v1 or can I use the pre-release now?

查看:93
本文介绍了我应该等待material-ui v1还是现在可以使用预发行版?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

构建一个React.js仪表板(数据表和图形),并使用 material-ui 对其进行样式设置.如果我现在使用的是预发行版本,那么在Material-ui v1发行时,我会做出更多更改吗?

Building a React.js dashboard (data tables + graphs) and styling this using material-ui. If I use the pre-release version right now, will I have make more changes when the v1 of material-ui is released?

推荐答案

我建议您尽快迁移.这并非微不足道,但您只需为使用新功能(例如,新的样式方式,CSS API,内置的网格系统/断点等)支付该价格.随着版本的发布,对v1所做的任何更改都应该更易于处理.通常,发行说明标识所有更改,并突出显示重大更改(如果有的话)被合并).

I'd recommend migrating as soon as you can. It is not trivial, but you pay that price once to use the new features (like the new approach to style, CSS API, built in grid system/breakpoints, etc). Any changes made to v1 should be easier to deal with as releases roll out. Generally, the release notes identify all of the changes, highlighting the breaking changes (if any were merged).

检查文档,并确保已使用所有组件.实施的.如果您发现v1尚未实现您依赖的组件,则有几种选择:

Check the documentation and make sure all of the components you're using have been implemented. If you find that v1 hasn't implemented a component you depend on, you have a few options:

  1. 实施并提交PR:)
  2. 实施临时版本并等待正式实施
  3. 使用纱线别名或通过添加自己的material-ui分支作为git依赖项/私有包
  1. Implement it and submit a PR :)
  2. Implement a temporary version and wait for the official implementation
  3. Run both versions of material-ui side by side using yarn aliases or by adding your own fork of material-ui as a git dependency/private package

这篇关于我应该等待material-ui v1还是现在可以使用预发行版?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆