jsex / yaml parser

Summary

• More descriptions everywhere.
• Fixed bug in get_deep: properties may be used multiple times
• Cleanup in yaml parser: list data types, property names
• Better mocks in jsex tests
• New yaml parser test for property inheritance

Focus

Mostly: Compatibility with previous use cases.

Test Environment

Run unit tests.

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues caosdb/customers/dimr/management#114
• Up-to-date CHANGELOG.md (or not necessary)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
  • How do I use the software? Assume "stupid" users.
  • How do I develop or debug the software? Assume novice developers.
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• Appropriate user and developer documentation (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

assigned to @daniel

marked the checklist item Annotations in code (Gitlab comments) as completed

requested review from @florian

marked the checklist item All automated tests pass as completed

added 1 commit

• e6a13890 - FIX: jsex: Better do_not_create

Compare with previous version

added 1 commit

• 90570a20 - DOC: jsex: Better docstring, a few new TODOs

Compare with previous version

marked the checklist item I understand the intent of this MR as completed

marked the checklist item Up-to-date CHANGELOG.md (or not necessary) as completed

marked the checklist item Appropriate user and developer documentation (or not necessary) as completed

marked the checklist item In-code documentation and comments are up-to-date. as completed

added 3 commits

• 1506041f - 1 commit from branch dev
• 117ae3a8 - Merge branch 'dev' into f-more-jsonschema-export
• b5660e94 - FIX: Correct usage of ui inline in unittest

Compare with previous version

marked the checklist item The test environment setup works and the intended behavior is reproducible in the test as completed

resolved all threads

approved this merge request

enabled an automatic merge when the pipeline for b5660e94 succeeds

mentioned in commit 06a3d145

merged