chore(release): version packages - #60
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
acture-forms-rjsf@1.1.0
Minor Changes
ea386c7: Accept
@rjsf6.x, and make the RJSF theme injectable.The
@rjsf/core/@rjsf/utils/@rjsf/validator-ajv8peer ranges move from^5.20.0to^5.20.0 || ^6.0.0.@rjsf/shadcnis published on the 6.x lineonly, so the old range made the shadcn theme — the one every frontend in this
ecosystem wants — impossible to install alongside this adapter. The failure was
an npm peer conflict at install time, i.e. before a line of form code got
written. No adapter code was needed to span the two majors:
@rjsf/core'sdefault export and
FormProps,@rjsf/validator-ajv8's default export, and theschema/formData/validator/liveValidate/onSubmit/ childrenprops are shape-identical on both.
<RjsfForm />gains an optionalformprop taking any RJSF theme's<Form />(ComponentType<FormProps>— the type every theme's default exportalready has), defaulting to the unstyled
@rjsf/coreform:Before this, the README told you to "pass your own
Formfrom the themedpackage" and there was no prop that accepted one. acture still bundles no UI kit
(hard-don't feat: Phase 4 (v1.0) + v1.1 — tier system, CLI, devtools, snapshot, tier warnings #8) — the theme is the host's, injected.
Both halves of the widened range are checked on every PR: the main CI job
installs and tests 6.x, and a second job installs its own plain 5.x tree and
typechecks + tests the adapter against it.
The
formvalue must be referentially stable (bind a theme at module level) —React reconciles by element type, so an inline
withTheme(...)remounts theform and discards in-progress input. Documented on the prop and in the README.
Also exported: the
RjsfFormComponenttype.