fix: not recursively camelCase keys in nested objects when using union with null #119
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 ought to fix #118.
The bug in the issue is due to the fact that the
type ObjectOptional
assumed only undefined (optional property), so I have fixed that part.Supplemental information on testing
Since the
type CamelCaseKeys
cannot be tested as is, it is tested by specifying thetype CamelCaseKeys
for the variable after conversion withcamelcaseKeys
.The test for
index.d.ts
before the modification failed as follows, but after the modification, the test passes because the union part works correctly.