-
Notifications
You must be signed in to change notification settings - Fork 105
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(ts): set payload to unknown value type #272
fix(ts): set payload to unknown value type #272
Conversation
edmundhung/conform#272 Until that is merged, we need to manually update it in node_modules
The TS team also suggests to use |
with manual edmundhung/conform#272
b8717a3
to
d2bcf1c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
The Jsonify utility used by Remix will make a `Record<string, any>` disappear in the type: remix-run/remix#7246 But considering this further, "unknown" is a safer option for this type anyway because it avoids issues with accidentally accessing the values off the submission payload without first checking them. So I do think this change should be made.
d2bcf1c
to
ede57a1
Compare
Any progress on this? 😬 |
I will update the remix fixture to v2 (pre) this weekend to verify the change and make a release. I was betting the issue to be resolved upstream soon so I don't need to bump the minor version now (This is a breaking change unfortunately). But it looks like |
The Jsonify utility used by Remix will make a
Record<string, any>
disappear in the type: remix-run/remix#7246But considering this further, "unknown" is a safer option for this type anyway because it avoids issues with accidentally accessing the values off the submission payload without first checking them. So I do think this change should be made.