-
Notifications
You must be signed in to change notification settings - Fork 49
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
fix(plugins): remove default queryables form value #1473
Conversation
Test Results 4 files ±0 4 suites ±0 6m 34s ⏱️ -1s Results for commit 04a088c. ± Comparison against base commit b247f5c. This pull request removes 1 and adds 2 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Code Coverage (Ubuntu)
Diff against develop
Results for commit: 04a088c Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Code Coverage (Windows)
Diff against develop
Results for commit: 04a088c Minimum allowed coverage is ♻️ This comment has been updated with latest results |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please test this fix
93182d0
to
1eb05e4
Compare
1eb05e4
to
19d9e27
Compare
for now the check was only on default eodag configuration and constraints file of the provider
'fetch_data()' must have been exposed to use it correctly in the test
remove 'fetch_data()' method and apply directly 'lru_cache()' on the result of '_fetch_data()'
19d9e27
to
04a088c
Compare
Fixes: #1450
When a queryable is called with an empty value (
""
,None
,[]
, etc.) indag.list_queryables()
, the returned default value of this queryable must be cleared in order to let other queryables depending on it list all their available values. Now, no default value is returned and the queryable appears as required.Moreover, if a queryable was called in
dag.list_queryables()
while it was neither a default value of the provider configuration nor in the provider constraints file but it was in the provider queryables form, an error was raised. This is possible now.fetch_data()
method has been exposed instead of being initialized inECMWFSearch
class initialization to make the code cleaner and allow the mock of this method in tests.