-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
v2 branch and roadmap #1409
Comments
I am currently using react-jsonschema-form from npm. What's the compatibility status of the following?
I am wondering if any of them have Bootstrap4 support as such, or if you're just expecting that Bootstrap3 will mostly work with Bootstrap4 (excepting glyphicons ... #1434 (comment) ) and that v2 is heading in the general direction of increased Bootstrap4 compatibility. I've assumed there are no versioning issues with React although I'm using mainly hooks-based functional components which render to include a react-json-schema Form component. If the discussion of the current compatibility status exists elsewhere, against which the roadmap of changes makes sense, then of course point me that way. |
react-jsonschema-form is going in the direction of being UI-framework-agnostic, with themes being able to be added through the Support for bootstrap 4 isn't blocked by a v2 version as such; it could be implemented now if someone made a bootstrap 4 theme (like the material-ui theme in #1420). v2 is more a way to add in breaking changes (such as requiring React 16 instead of React 15). |
Any sense of the approximate timeline for a v2 release? |
v2 is now out. Thanks to all who helped get this out! |
Thanks for this release. However I'm having some issues while updating the version with npm.
|
@kim1882 |
We should get out a v2 soon so we can resolve some of the issues that require backwards-compatible changes. Let's use this issue for discussion of a roadmap, plans, and issues.
Tracking some of the things we might want in v2 in this GitHub Project board. Feel free to suggest what you think should / shouldn't be on this board.
I've also created a v2 branch. If you are able to help out with some of those changes, please make PRs to the v2 branch. As we continue with work on v1, we can periodically merge master in v2.
Once v2 is released, we will rename the current master branch to v1 and rename v2 to master. In the future, v1 may only be updated with bugfixes and/or security enhancements.
The text was updated successfully, but these errors were encountered: