-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WP3 Validation of process metadata: test_process_metadata_functional() should ignore non-functional metadata in parameter schema #54
Comments
non-functional parameters are skipped with See the docs in readme about "WP3 Validation of process metadata":
|
There's was a mistake in last sentence. I have made the edit. |
ok, I understand now, you are talking about non-functional fields in the schema of process parameters. The parameter's schema is indeed being compared as a whole currently: openeo-test-suite/src/openeo_test_suite/tests/processes/metadata/test_process_metadata.py Lines 79 to 80 in 5b9727d
Do you have some concrete examples of differing parameter schema's? |
A couple of examples where even schemas are meant to be updated by implementations:
|
test_process_metadata_functions() from src/openeo_test_suite/tests/processes/metadata/test_process_metadata.py, check values within functional and non-functional parameters. For example, this function also tests for description, which is present in the schema parameter. Like
"id": "array_append", "parameters": [ { "description": "Value to append to the array.", "name": "value", "schema": { "description": "Any data type is allowed." } }
This should not happen if
-m "not optional"
is added to the command.The text was updated successfully, but these errors were encountered: