Skip to content
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

Fix #103: Disabling readonly anyOf/oneOf fields #104

Merged
merged 1 commit into from
Dec 31, 2024

Conversation

glitchassassin
Copy link
Contributor

No description provided.

@bhch
Copy link
Owner

bhch commented Dec 10, 2024

Thanks for the PR.

Can you please include only the src files in the commit and exclude dist and other files outside of src.

dist builds are committed only for new releases.

Other than that, everything looks good.

@glitchassassin glitchassassin force-pushed the 103-readonly-oneof-anyof branch from 487e1a1 to 73dba6c Compare December 10, 2024 19:34
@glitchassassin
Copy link
Contributor Author

Done!

@glitchassassin
Copy link
Contributor Author

@bhch just checking back in - anything else you need from me on this?

@bhch bhch merged commit 849e736 into bhch:master Dec 31, 2024
@bhch
Copy link
Owner

bhch commented Dec 31, 2024

Sorry to have kept you waiting. I've merged the changes. I'll do a release in a few days.

BTW, I'm currently working on a new library for generating JSON Schema forms. It will be completely customizable with the ability to write custom widgets, plugins etc, and a good development experience (with storybook etc.).

Repo: https://github.com/topspin-js/topspin. I haven't pushed anything yet but I will soon (I'm trying to clean up my local copy before pushing the code).

Again, thanks for the PR and wish you a happy new year.

@bhch
Copy link
Owner

bhch commented Jan 29, 2025

Fixed in v2.14.4.
Also released in django-jsonform v2.23.2.
Please update and test it out.
Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants