Merlin Beutlberger

Also, please share your npm version as well as your operating system with us. Thanks!

Thank you very much for this PR! We'll discuss it in the team and get back to you. > Any reason why text path is the full path and json...

I reviewed the code already last week and have no objections. Regarding the paths I think we should format them relative to the project root. In addition, we played around...

We moved the summary to the top. Sorting is now by severity (order: Fatal Errors, Errors, Warnings), then line, then column. The output looks like this now: Updated Table output...

LGTM and I'm fine with using this for the time being. I still find the signature somewhat complicated. It would be nice if we could limit it to a few...

Thanks for reporting. Excluding/Ignoring files is already planned and listed on our roadmap: https://github.com/SAP/ui5-linter/issues/21

This is a very reasonable enhancement. We could also add support for projects of type `module`. But from what I can see this still wouldn't help you since your `ui5.yaml`...

See https://github.com/SAP/ui5-tooling/issues/45#issuecomment-2152106687 😉

| Legacy API and Migration Plan | Notes | |--------|--------| | [`attachInit(fnFunction)`](https://ui5.sap.com/#/api/sap.ui.core.Core%23methods/attachInit) Migrate to `Core#ready(fnReady?)` | | | [`attachInitEvent(fnFunction)`](https://ui5.sap.com/api/sap.ui.core.Core#methods/attachInitEvent) Migrate to `Core#ready(fnReady?)` | | | [`getControl(sId)`](https://ui5.sap.com/#/api/sap.ui.core.Core%23methods/getControl) Migrate to `sap/ui/core/Element.getElementById(sId)` |...

@NAVI-91 based on your description, I don't think this is the same issue. Please raise a dedicated issue or SAP support incident The issue discussed in this incident has been...