fix(typings): incompatible type issue for nested strict object schemas#2785
Closed
LeoAso wants to merge 1 commit intohapijs:masterfrom
Closed
fix(typings): incompatible type issue for nested strict object schemas#2785LeoAso wants to merge 1 commit intohapijs:masterfrom
LeoAso wants to merge 1 commit intohapijs:masterfrom
Conversation
|
@LeoAso What is the state of this? We are heavily relying on this and have a lot of workarounds we'd like to get rid of :) |
Author
|
@phillip-kil It seems the maintainers haven't gotten around to reviewing it yet. |
Collaborator
|
This looks fine, although, would you mind adding tests in this file to avoid any further regression? |
Collaborator
|
Superseded by #2836, thanks for doing the initial work though! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The type issue that prevented strict object schemas from being nested has been resolved. The following is no longer incorrectly flagged as an error.
This PR fixes #2764.