Add ability to disable rule for a particular BPMN file or element

[nhomble]

Is your feature request related to a problem? Please describe

I am forced to disable a certain rule in my project even though it is only one bpmn in the project that requires this rule exclusion.

Describe the solution you'd like

I would prefer to disable the bpmn lint rule for a specific file.

A possible solution would be to support exclusions in the .bpmnlintrc file.

Describe alternatives you've considered

I could keep the rule and skip linting the file in general, but then there are other important lints that I still want to evaluate. I don't have a use case for ever skipping them.

Additional context

This is a similar use case to the eslint-disable pragma for eslint.

[nikku]

Thanks for opening this issue, I can see how it could be very useful.

What would be your preferred solution?

• Add the eslint-disable like pragma to your BPMN file
• Add custom overrides (exclusion) in .bpmnlintrc file

[nhomble]

My preference depends on the modeler. If adding an exclusion as some kind of property or pragma on the xml is wrapped in a nice UI, then I think keeping the exclusions in the same file could be really helpful. It would also be ideal to target very specific nodes of the xml that require exclusions rather than the whole file.

Without some GUI support, I don't think people would want to open the raw xml every time. I'd prefer the .bpmnlintrc approach as an mvp.

[nikku]

Thanks for your feedback. From the bpmnlint perspective we may want to support both cases. It is GUI-less anyway. Once we support tagging inside the BPMN file then we could consider a better editor integration.

[nikku]

We'd be happy to work with you to get this feature incorporated, if you are interested in contributing.