Replies: 3 comments
-
|
this would be very helpful for some tooling we're working on as well |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I'm just realizing that the naming is confusing; todos are ignored by default, so it should probably be |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Found another way to get to this data - hoping to be able to get this merged: #397 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
For editor integration through packwerk-vscode, I'd love to be able to see all the violations, even the todo-listed ones. I would also like this output for downstream analysis tools so that I don't have to use
parse_packwerkwhich works on the todo-list files. Those files omit some information that the output ofpackwerk checkincludes or can include with a custom offense formatter.If
packwerk checkhad a--ignore-todosoption, that would support my use case. Would anyone else be interested in this feature?Beta Was this translation helpful? Give feedback.
All reactions