Thanks a lot! Tangential question: can you somehow annotate the exclusion of a specific warning, by somehow writing somewhere “This is actually fine because so-and-so”, like you can do with code linters?
Just right click on any error message in the ERC window and select Exclude this Violation
This greys out the message, and you can also reset this:
You can turn on or off the excluded items with the checkboxes at the bottom.
If they are turned off, they don’t show at all.
1 Like
no you can’t, but this would be a reasonable feature request.
Also: in this case, I really don’t recommend ignoring this warning. It would be easy to accidentally overwrite your changes while updating other footprints. The best resolution for this warning is to copy the footprint into an editable library and make the modifications there.
1 Like
Huh?
Yes you can. Via the ERC (and DRC) dialogs you can either exclude specific types or individual messages as I showed with the screenshots above.
The OP was asking if you can annotate an exclusion with a specific note about why you are excluding it.
Thanks again for your detailed answer! My second question was about annotating those exclusions, in a free-form text where you could explain why this violation was ignored. In Pylint, for example (borrowed from stackexchange), you can do:
from typing import NoReturn, Optional # pylint: disable=unused-import # Note: we actually need this import, because…
So future readers (including yourself!) can understand why you’re disabling a specific warning.
Oopsie. indeed annotations for the exclusions are not supported in KiCad.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.