-
Notifications
You must be signed in to change notification settings - Fork 25
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: proper use of type from ui builder backend #317
fix: proper use of type from ui builder backend #317
Conversation
Codecov Report
@@ Coverage Diff @@
## main #317 +/- ##
==========================================
- Coverage 89.63% 89.56% -0.07%
==========================================
Files 36 36
Lines 1244 1246 +2
Branches 278 278
==========================================
+ Hits 1115 1116 +1
- Misses 126 127 +1
Partials 3 3
Continue to review full report at Codecov.
|
lgtm, but lets also get a review from @alharris-at/@dpilch on this pr as I am not too familiar with this section of the code |
also, I think you might want to push this pr to develop instead of main. We generally push changes into develop first, and merge into main when we do the release |
// object, array, and null | ||
case 'object': | ||
return factory.createJsxExpression(undefined, jsonToLiteral(parsedValue)); | ||
default: |
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.
Can you add test cases for these scenarios? Type mismatch case as well.
018f0e5
to
d134a65
Compare
d134a65
to
179ef02
Compare
Description of changes:
JS types specified in the type prop is in lowercase, and all of the values pulled from the backend are string literals. Updating the function to take those into account