ANNOUNCEMENT: Breaking changes planned for v4

[epicfaace]

The next version of rjsf will be v4. I'm going to start making a running issue like this for each breaking change so it's easier to organize what we want to get in for each major release version.

Planned breaking changes

PRs that are nearly ready and will hopefully be added in v4:

• refactor: types for withTheme refactor: types for withTheme #2279
• Maintain AJV properties when custom validator is in use. Maintain AJV properties when custom validator is in use. #2002
• Remove componentWillReceiveProps from Form.jsx Remove componentWillReceiveProps from Form.jsx #2010

Other potential changes

If someone makes PRs for these issues, we might be able to get them into v3.

• noHtml5Validate should be true by default noHtml5Validate should be true by default #1184
• Fieldset preventing flexbox styling Fieldset preventing flexbox styling  #762

These PRs would be good to add, but still have some work to do on them:

• support if/then/else, breaking change is removing the dependency on json-schema-merge-allof Optimizations to improve performance on complex conditional schemas #2466

Have suggestions for changes / additional items we should add to this list? Feedback welcome!

cc @ri0ter @erunion @stanlemon @mattcosta7 @zepatrik @wegry @jimmycallin @RoboPhred @bmmpt

[jimmycallin]

Great job with the v3 release!

I think my comments from the v3 issue still stands regarding react strict mode, which is related to this PR and its discussions #2010

[epicfaace]

Okay, added it to the list!

[xgenvn]

Is it possible to separate the parser logic (in core) into a subpackage? I know the r is for react, but if we make the core more generic, I think it's easy to implement in another framework.

[epicfaace]

Which kind of logic are you referring to?

…

-- Ashwin Ramaswami

On Thu, Jul 1, 2021 at 5:44 AM Anh Tu Nguyen ***@***.***> wrote: Is it possible to separate the parser logic (in core) into a subpackage? I know the r is for react, but if we make the core more generic, I think it's easy to implement in another framework. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2437 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAM4MXYKN53E45QPUJJGH5TTVQ2GBANCNFSM47KBX2LQ> .

[xgenvn]

@epicfaace Hi, I refer to the parser from JSONSchema (model) and UI Schema into abstract inputs/controls. I'm kind of Vue-guy, and there is no match implementation for JSONSchema-based form rendering. If there is an abstract layer for the view and reactive state, it's possible to add Vue support as well.

[epicfaace]

That's a good idea. Is this something whose design / code you'd be willing to contribute?

…

-- Ashwin Ramaswami

On Thu, Jul 1, 2021 at 10:17 AM Anh Tu Nguyen ***@***.***> wrote: @epicfaace <https://github.com/epicfaace> Hi, I refer to the parser from JSONSchema (model) and UI Schema into abstract inputs/controls. I'm kind of Vue-guy, and there is no match implementation for JSONSchema-based form rendering. If there is an abstract layer for the view and reactive state, it's possible to add Vue support as well. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2437 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAM4MX5S5DVPLMWOKGE23DLTVR2H7ANCNFSM47KBX2LQ> .

[xgenvn]

@epicfaace I think I can contribute to this if it's getting more attention. At the moment I'm referencing the schema for a Vue implementation. I guess the parsing part will be similar.

[epicfaace]

Yes, that would be great! Do you want to maybe outline a design for this in a design doc (maybe Google Docs) so we can figure out the best way to go about this?

…

-- Ashwin Ramaswami

On Thu, Jul 1, 2021 at 10:40 AM Anh Tu Nguyen ***@***.***> wrote: @epicfaace <https://github.com/epicfaace> I think I can contribute to this if it's getting more attention. At the moment I'm referencing the schema for a Vue implementation. I guess the parsing part will be similar. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2437 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAM4MXYJDQ7PPADGDGVODIDTVR46TANCNFSM47KBX2LQ> .

[xgenvn]

@epicfaace I will spend some time digging into the current implementation first and will try to outline the design. I think for in-depth discussion, we can continue on Discord. Thanks for hearing the idea!

[ssbyoung]

Not sure if #2456 is worth considering for this release or the next one.

[tm1000]

What about hooks support? EG rewriting the class components to be functional hook components instead

[Zakhar-Kutsko]

Hi there! When do you plan to release a new v4 version?

[epicfaace]

This Friday

…

-- Ashwin Ramaswami

On Wed, Feb 16, 2022 at 8:08 AM Zakhar-Kutsko ***@***.***> wrote: Hi there! When you plan to release a new version? — Reply to this email directly, view it on GitHub <#2437 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAM4MXZLHTF57FJTGDN5XB3U3OOUVANCNFSM47KBX2LQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>