Awesome, let me know how it goes :)
@nombrekeff I've released a new version, which supports some basic configuration through a "p42.toml" file in the workspace root.
To disable a refactoring, add a section with "refactoring.$refactoring-id" and set enabled to false, for example:
[refactoring.optional-chaining] enabled = false
The refactoring ids are displayed as grayed-out text in parentheses in the hover messages.
Wow nice, such fast implementation, kudos to you!
I haven't been able to try it yet, but will do soon
It took a while longer, but excluding individual statements from the P42 analysis is now also possible with '// p42:ignore-next-statement'.
This small addition is super helpful beyond the VS Code plugin, in excluding unwanted suggestions in automated P42 pull request and commit reviews :)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Awesome, let me know how it goes :)
@nombrekeff I've released a new version, which supports some basic configuration through a "p42.toml" file in the workspace root.
To disable a refactoring, add a section with "refactoring.$refactoring-id" and set enabled to false, for example:
The refactoring ids are displayed as grayed-out text in parentheses in the hover messages.
Wow nice, such fast implementation, kudos to you!
I haven't been able to try it yet, but will do soon
It took a while longer, but excluding individual statements from the P42 analysis is now also possible with '// p42:ignore-next-statement'.
This small addition is super helpful beyond the VS Code plugin, in excluding unwanted suggestions in automated P42 pull request and commit reviews :)