You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @gmlewis, surely this is an issue with the Python "jschon" package making assumptions about definition names? Generally speaking, snake-case is the preferred option for URLs as they avoid potential issues with file system case sensitivity and maintain coherence with the domain name. I'd be reluctant to make such a massive change without a rock-solid reason!
I would however be in favour of flexibility. If someone would like to override the default snake-case in the reflector configuration, then it makes sense to allow that. This may be a better approach for your PR.
I would however be in favour of flexibility. If someone would like to override the default snake-case in the reflector configuration, then it makes sense to allow that. This may be a better approach for your PR.
Thank you for the feedback, @samlown !
I've attempted to do this. PTAL.
Structs are currently rendered as kebab-case in the
"$id"
field.For example,
TestUser
becomes:When another field attempts to reference this struct, the Python3.10 "jschon" package resports this error:
but if the
"$id"
line is changed fromtest-user
toTestUser
, then the "jschon" package parses the file successfully.I will work on a PR for this issue.
The text was updated successfully, but these errors were encountered: