Repository navigation
Conversation
gnom7
force-pushed
the
target-type-import-fix
branch
from
October 26, 2026 16:29
222e794 to
1619cd9
Compare
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.
Hello, could you please validate and merge or provide feedback on how PR should be refined.
My use-case that I'd like fixed is basically described in the test.
I'm trying to implement PATCH semantic from box type similar to JsonNullable and so my
@Conditionaldepends on the target type - if I map to another box I have to treat value as-is, if I map to raw type I have to apply PATCH semantic and report absent for absent (undefined) JsonNullable so that value is just ignored.Could you please let me know if there is a planned release date for 1.7.0/1.6.4?