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
When using a version of dandischema that's behind DANDI_SCHEMA_VERSION, the local schema is not used, but rather the schema is fetched from dandischema releases. The code shown below is where this occurs
This is rather confusing behavior if you're relying on modifications to the local schema, like using localhost urls, since the schema that is used for validation will be independent of any changes you have. Is there some way this can be improved?
The text was updated successfully, but these errors were encountered:
@AlmightyYakob - if you are making changes to the schema, then the schema version has to be updated in consts.py. a prior schema version does not correspond to the current schema. the pydantic branch of the code only validates against the current schema.
When using a version of dandischema that's behind
DANDI_SCHEMA_VERSION
, the local schema is not used, but rather the schema is fetched from dandischema releases. The code shown below is where this occursdandi-schema/dandischema/metadata.py
Lines 174 to 187 in 6e99462
This is rather confusing behavior if you're relying on modifications to the local schema, like using localhost urls, since the schema that is used for validation will be independent of any changes you have. Is there some way this can be improved?
The text was updated successfully, but these errors were encountered: