-
Notifications
You must be signed in to change notification settings - Fork 50
fix(plugins): adapt queryables additional_properties to providers config #1646
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
Conversation
Code Coverage (Ubuntu)
Diff against develop
Results for commit: ee0e9e6 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Code Coverage (Windows)
Diff against develop
Results for commit: ee0e9e6 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
360bfa6
to
ae423cb
Compare
ae423cb
to
96d3e7a
Compare
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.
When I select one specific product type of cop_marine, additional_properties is still true although they are not available.
When I select one specific product type of cop_marine, additional_properties is now False like it shoudl be. Can You check on your side @jlahovnik ? |
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 add a simple test to check additional_properties
in 2 different providers queryables
refactor: simplify code Co-authored-by: Sylvain Brunato <61419125+sbrunato@users.noreply.github.com>
I added a simple test to check additional_properties in 2 different providers queryables with cop_marine et peps |
fix: add suggestions Co-authored-by: Sylvain Brunato <61419125+sbrunato@users.noreply.github.com>
No longer force
additional_properties
toTrue
. Usediscover_metadata.auto_discovery
value fromproviders.yml
instead.ref #1642