feat: support PEP 735#208
Conversation
405e4ee to
2b38147
Compare
2b38147 to
6fbb97e
Compare
|
|
6fbb97e to
0a2ed51
Compare
0a2ed51 to
288300e
Compare
I'm fairly sure this is right. There's no generic mechanism in JSON Schema for referring to the literal keys of an input object as far as I know. |
|
Added a dynamic check for this case. Circular deps could probably be done too but I'm tempted to wait till we are 3.9+, since IIRC this is easy with graphlib. |
abravalheri
left a comment
There was a problem hiding this comment.
Thank you very much @henryiii for working on this.
Signed-off-by: Henry Schreiner <[email protected]>
Signed-off-by: Henry Schreiner <[email protected]>
Co-authored-by: Anderson Bravalheri <[email protected]>
Co-authored-by: Anderson Bravalheri <[email protected]>
Co-authored-by: Anderson Bravalheri <[email protected]>
d0b2808 to
8ba8e1b
Compare
Add support for validating PEP 735.
Pretty sure we can't validate that include-groups point to an existing group without custom code. Though maybe there is custom code for
dynamicalready? It doesn't seem to be part of the schema like in SchemaStore's version.