See #197. After the premature merge and following revert of !103 (merged), this MR re-introduces the changes.
TODO: Make these changes compatible to caosadvancedtools.
This MR has diverged very much from dev! It's probably easier to create a new MR with these changes based on the current dev branch.
The main problem is:
Point the reviewer to the core of the code change. Where should they start reading? What should they focus on (e.g. security, performance, maintainability, user-friendliness, compliance with the specs, finding more corner cases, concrete questions)?
Apart from unit tests, also check manually with caosdb crawler and advanced user tools.
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
For further good practices have a look at our review guidelines.