-
-
Notifications
You must be signed in to change notification settings - Fork 541
fix(form-core): fix DeepValue from record values being wrong #1558
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
base: main
Are you sure you want to change the base?
Conversation
|
View your CI Pipeline Execution ↗ for commit d586448
☁️ Nx Cloud last updated this comment at |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1558 +/- ##
==========================================
+ Coverage 90.35% 90.53% +0.18%
==========================================
Files 38 38
Lines 1752 1807 +55
Branches 444 466 +22
==========================================
+ Hits 1583 1636 +53
- Misses 149 151 +2
Partials 20 20 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
thank you for fixing this! is there a timeline on when it will be included in a release? 👀 |
|
@binajmen Well, the main issue is that this isn't really a fix. This PR has been a bit stale because of that ... but I'm not sure there will be a convenient solution that doesn't need reworking all of the DeepKeys types |
|
I made progress! It now shows possible values as union instead of an intersection. Will commit the changes tomorrow. |
|
Closes #1551
This PR fixes a wrong intersection that occurs when iterating over template strings (such as records).
The issue arose because of TypeScript inferring the following:
Important
TypeScript has a limitation with template string types. Nested records are not yet safe. Example below: