add configuration options

[larshp]

add configuration options

[larshp]

Hi,

abaplint defaults: everything is enabled by default, this is to allow easy discovery of rules, some rules might even conflict internally, but decisions have to be made. Finding any common ground is difficult, some rules are stupid and only applies in some scenarios, its up to the users to build their default as per their development guidelines.

but, I'm open to adding a configuration in the local IDE to override the rules of the repository(eg. disable rules)

[TheLazyHangman]

Good afternoon Lars,
did this feature ever get an update? I'm asking here but this could be relevant also for #69, since that's the actual scenario I'd like to get more comfortable with in VSCode. I just didn't want to spam the same question in all related topics.

Kind of on a related note though, there are just two options I'd like to get rid of, but of course I'not going to ask you to update the defaults just because I'd like to change two minor rules. So my question is: is there a chance you could set up some kind of poll to review the current default rules and maybe find a common ground on which we could build a newer version that's suitable for more users? I understand that the requirement to have a custom set of rules for remotefs has been shared in the past, so maybe we can all just find some sort of agreement about what could be updated?

[TheLazyHangman]

Thanks for the quick response.
Since building custom defaults isn't supported in remotefs, adding a configuration in the local IDE seems like the way to go.

Best regards and thanks again for the excellent work so far.

[larshp]

pull requests welcome 😄