Wraps function types in additional brackets to prevent broken union types #400
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.
E.g. take this schema:
Without brackets, a chain would have become
In this type, the whole
any | { json: any; } | { raw: string; }
is the return type of the function, which is wrong.With brackets, it will be:
There could be some more advanced logic to figure out if we want the brackets or not depending if we're using a union or not, but I feel it is even safer in general to just wrap function types in brackets given the "unsupported" nature of the Function type.
Note: this will conflict on merge with #401. I'll take care of it if merged. Probably one test will fail.