Improve handling of reading structuraly invalid metadata
@phanak-sap is already working on this.
Since Jan 26, 2021.
Assessment
This issue has not been assessed yet.
Description
Currently, in CLI run there is information about that (pyodata errors) but then the program exits, not logging the same information to text logger. This should be fixed.
Additionally, in bumped pyodata 1.7.0, is new option for explicit checking of metadata validity - service.schema.is_valid. Odfuzz should utilize it on the first request for metadata
- Dominant language
- Python
- Stars
- 23
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SAP/odfuzz
-
Bug in CLI runner Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
code improvements
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100