Thanks, Sebastian,

�� This worked and solved my problem. For future readers, these changes get added to a Manifest<Package-Name> class and make their way into the git repo and the mages that load the baseline in that repo.

�� It would be nice for a visible pragma to live near the code that triggers the warning that the pragma is suppressing, but having a way to do this is much better than not having a way.

Thanks again,
Eric

On Wed, Aug 31, 2022 at 12:04 PM Sebastian Jordan Montano <sebastian.jordan@inria.fr> wrote:
Hello,

I don't know about any pragma, but you can deactivate the lint rule to only one method. You need to click on the "x" that is next to the name of the rule and then select the option that you prefer. This will create a Manifiesto class that contains the information of which rules to ban on to which context.


Cheers,
Sebastian Jordan

De: "Eric Merritt" <eric@merritt.tech>
��: "pharo-users" <pharo-users@lists.pharo.org>
Envoy��: Mercredi 31 Ao��t 2022 15:18:07
Objet: [Pharo-users] Is there a pragma to disable a critic for a particular method?
Hello Everyone,

While I take the critiques seriously, there are times when I will intentionally disregard a specific warning. In these cases, in other languages, I have found it useful to indicate that I am disregarding a warning by adding a pragma to disable that particular warning. I have been looking for similar functionality in Pharo. I found an old (circa 2009) reference to <lint> and <ignoreLintRule> pragmas, but those seem to no longer work.

Is there currently a way to disable a specific warning in a method?

Thank you,
Eric