fix Ensure useFormContext always returns a valid context

[minai621]

Description

This pull request addresses the issue where the useFormContext function could potentially return undefined, leading to instability in the register function. Given that defaultInjectionKey is provided, this situation should not occur. The useFormContext function has been updated to cast the injected value directly to FormHandlerReturn<T>, ensuring that it is always a valid context.

Changes Made

• Updated useFormContext to cast the injected value to FormHandlerReturn<T>, ensuring it is always valid.
• Improved the stability of form context usage.

Issue

This pull request resolves issue #73.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
vue-form-handler	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 13, 2024 3:12pm

[dbssman]

Description

This pull request addresses the issue where the useFormContext function could potentially return undefined, leading to instability in the register function. Given that defaultInjectionKey is provided, this situation should not occur. The useFormContext function has been updated to cast the injected value directly to FormHandlerReturn<T>, ensuring that it is always a valid context.

Changes Made

• Updated useFormContext to cast the injected value to FormHandlerReturn<T>, ensuring it is always valid.
• Improved the stability of form context usage.

Issue

This pull request resolves issue #73.

The assumption that since defaultInjectionKey is provided this does not occur is not correct, since you could be using the defaultInjectionKey but adding a different one at top level or reverse.

In any case, I do think this provides value and is, in general a good idea, since having to cast it manually is quite annoying.

I will include this fix in the next release :) thank you for contributing!

[minai621]

@dbssman
Thank you for your detailed review and for pointing out the potential issue with the defaultInjectionKey assumption. I appreciate your positive feedback and am glad to hear that the fix will be included in the next release. Thank you for the opportunity to contribute! If you prefer, feel free to close the PR.