-
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
ANNOUNCEMENT: Breaking changes planned for v3 #2297
Comments
@epicfaace I was hoping the react-is bump might make it into v3 as well. #2196. |
Oh, is that a breaking change? If not, we can still get it in either in v3 or sometime later, but the scope of this issue is just categorizing the breaking changes (because they have to be released on a new major bump). |
Sounds good.
I don't believe so. Just something I've been hankering for. |
@epicfaace sounds good to me. I noticed there's a few things tagged with 'deprecated' in the codebase. might be a good time to clean those as well. Particularly
|
Sounds good! Might want to look into the discussions in this PR and consider them as well #2010 |
Some thoughts...
|
@epicfaace You also mentioned this old PR of mine to be a breaking change #1522 might be time to merge it then (or let me know if you want me to revert the breaking change part). personally i would love to see rjsf to be strict mode valid as a part of v3. |
@epicfaace Please consider including #2272 |
@gsstar9028 no worries, it's already been merged into master, so it will be included! |
@jimmycallin Agreed, that would be nice! (so we'd need to stop using unsafe component lifecycle methods) Sorry for the delay in responding to your other PR. |
It's been quite a while since I made this post, so I'm going to go ahead and release v3 soon so we don't have too much time lag between versions. We can release the other pending breaking changes in v4 (which could probably come relatively soon after v3 and have less breaking changes). |
Is there going to be support for the JSON Schema v7 conditionals? https://json-schema.org/understanding-json-schema/reference/conditionals.html |
Not now, but maybe we can track that in another issue. |
That would be awesome because we might be forced to use it in our schema given some constraints we have |
@epicfaace do you need any help with anything prior to v3 going out? I'd like to help carry this over the hump if possible. |
@wegry Thanks for checking. I'd like to clean up https://github.com/rjsf-team/react-jsonschema-form/blob/master/docs/3.x%20upgrade%20guide.md (ensure that the tone is consistent, everything is clear, etc.) before release because multiple people have added to it and it doesn't read very well at the moment. |
The next version of rjsf will be v3, and we'll add a few breaking changes to it.
Planned changes
PRs that are nearly ready and will be added in v3:
Other potential changes
If someone makes PRs for these issues, we might be able to get them into v3.
These PRs would be good to add, but still have some work to do on them:
json-schema-merge-allof
Implementation of If Then Else / Const v2 #1666Have suggestions for changes / additional items we should add to this list? Feedback welcome!
cc @ri0ter @erunion @stanlemon @mattcosta7 @zepatrik @wegry @jimmycallin @RoboPhred @bmmpt
The text was updated successfully, but these errors were encountered: