[Snyk] Upgrade react-hook-form from 7.4.0 to 7.35.0 #689
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 automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade react-hook-form from 7.4.0 to 7.35.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: react-hook-form
🎉 feature: new type
FieldPathByValue
field path by value generic implementationTFieldValues extends FieldValues,
Path extends FieldPathByValue<TFieldValues, Date>
>({ control, name }: { control: Control<FieldValues>; name: Path }) {
const { field } = useController({
control,
name,
});
}
function App() {
const { control } = useForm<{
foo: Date;
baz: string;
}>();
return (
<form>
<CustomFormComponent control={control} name="foo" /> {/* no error /}
<CustomFormComponent control={control} name="baz" /> {/ throw an error since baz is string */}
</form>
);
}
🛵 close #8969 improve type for useFieldArray rules validate prop #8974
🛗 upgrade to TS 4.8.0 and Jest 29 #8620
🐞 fix #8970 register field array cause render issue #8972
🐞 fix: typings for useWatch() with no arguments #8923
🐞 fix #8919 make
useController
fieldState
properties enumerable👶🏻 close #8909 form context children prop type (#8910)
🐌 allow field errors to escape type check when provided with any type
🔐 github workflows security hardening #8965
💚 ci: stop csb ci from publishing a comment on PR (#8977)
thanks to @ Moshyfawn, @ sashashura, @ carvalheiro, @ chetvishal and @ MicaelRodrigues
🎉 feature: new type
FieldPathByValue
field path by value generic implementationTFieldValues extends FieldValues,
Path extends FieldPathByValue<TFieldValues, Date>
>({ control, name }: { control: Control<FieldValues>; name: Path }) {
const { field } = useController({
control,
name,
});
return null;
}
function ExampleOfUsage() {
const { control } = useForm<{
foo: Date;
baz: string;
}>();
return (
<div>
<SomeCustomFormComponent control={control} name="foo" />{" "}
{/* throw no error /}
<SomeCustomFormComponent control={control} name="baz" />{" "}
{/ throw an error since baz is string */}
</div>
);
}
🐞 fix #8919 make useController fieldState properties enumerable
👶🏻 close #8909 form context children prop type (#8910)
🐌 allow field errors to escape type check when provided with any type
thanks to @ carvalheiro, @ chetvishal and @ MicaelRodrigues
Revert "🧳 let
isSubmitting
state update after valid form (#8829)"Read more
Read more
Read more
Read more
Read more
Read more
Read more
Commit messages
Package name: react-hook-form
TypeError: Class constructor cannot be invoked without 'new'
vercel/next.js#8973)Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs