feat: add warning messages if the response has a "messages" key with a non-empty list value #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #28. This is the last PR before the 2.5.0 release.
Added the feature to log warning messages. There is also another module called "warning", but logging seems better in this case because I found the "warning" message only warns once for the same code line, which is not what we want.
Also added a flag (default True) in the ONC class so that users can turn off the warning information if they would like.
From what I understand, only
/dataProduct/delivery
and scalar/raw data web services have this "messages" key in the response.I tested it by running (code snippet borrowed from #4 )
It outputs