Correctly handle recursive schemas in -parser-info - #1234
Merged
mattiuusitalo merged 8 commits intoOct 31, 2025
Conversation
GPT-4.1 LLM used for debugging, design, and to generate the basis for the for the (extend-type Object ParserInfo ...) case.
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
3 participants
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.
Fixes metosin/oksa#27
Detects ref cycles by identifying refs by their name+scope. Generalizes a concept from malli.generator, so a shared helper
m/-identify-ref-schemaseemed appropriate since it's quite handy. It could be used in place of-memoizein:ref's validator. Unfortunately there's nooptsarg so dynamic vars might be needed.GPT-4.1 LLM used for debugging, design, and to generate the basis for the for the
:ref-parser-infocase (based on-ref-gen).