This was already merged and approved in !137 (merged), but caused problems downstream. Merge this when crawler and advancedtools are compatible. Possibly add unittests, depending on reasons for failures.
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)?
How to set up a test environment for manual testing?
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.