Skip to content

Suppression naming convention and clarification over methodology used #126

Description

@georgeRobertson

Describe the bug
The suppression function is ambiguous and does not clarify which methodology of suppression that is being used.

To Reproduce
Steps to reproduce the behaviour:
N/A

Expected behaviour
Current behaviour of the function is fine so long as it's following the methodology given

Screenshots
If applicable, add screenshots to help explain your problem.

System (please complete the following information):

  • OS: N/A
  • Python: N/A
  • Version: Current

Additional context
Steps needed to fix current issue:

  1. Rename the current suppression function so that it represents the methodology that it is following
  2. Add appropriate documentation or links to the methodology used

Metadata

Metadata

Labels

documentationImprovements or additions to documentationenhancementNew feature or requestinvalidThis doesn't seem right

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions