Remove @fabrix-framework/fabrix/rhf export #20
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.
Fabrix internally uses react-hook-form to manage form states and was exposing
@fabrix-framework/fabrix/rhf
to provider users with the same version of react-hook-form. This is a adhoc workaround toward the behaviour thatuseController
hook in component registries does not access the same version of react-hook-form that fabrix internally mounts asFormProvider
.However, I found that adding react-hook-form a peer dependency also works out. Exposing RHF from fabrix was a bit clumsy, so this PR is a fix for that.