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
Currently we don't use strictify on nsfs_config_schema.
Currently we use ajv.validate(schema_name, object_to_validate) and it doesn't align with the avj documentation (here), please notice the comment "Best performance: compile and getSchema methods".
Expected behavior
Use strictify on nsfs_config_schema with additionalProperties: true.
Compile the validate function once and re-use it (details in the link attached above).
Steps to reproduce
none (internal change).
More information - Screenshots / Logs / Other output
Notes:
Currently, we would get errors trying to strictify on nsfs_config_schema. Partial things I found:
The schema uses default keyword which we didn't have in our past schemas (probably need to edit strictify for that case).
The schema uses description which is unknown keyword, and can be replaced with doc.
The schema uses array, but does not use items under it.
Might need general refactoring in the nsfs_config_schema so we would not get errors on strictify.
The text was updated successfully, but these errors were encountered:
Environment info
Actual behavior
strictify
onnsfs_config_schema
.ajv.validate(schema_name, object_to_validate)
and it doesn't align with the avj documentation (here), please notice the comment "Best performance: compile and getSchema methods".Expected behavior
strictify
onnsfs_config_schema
withadditionalProperties: true
.Steps to reproduce
More information - Screenshots / Logs / Other output
Notes:
Currently, we would get errors trying to
strictify
onnsfs_config_schema
. Partial things I found:default
keyword which we didn't have in our past schemas (probably need to editstrictify
for that case).description
which is unknown keyword, and can be replaced withdoc
.array
, but does not useitems
under it.nsfs_config_schema
so we would not get errors onstrictify
.The text was updated successfully, but these errors were encountered: