You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, suppressions only allow you to target a specific path. If that path is then expanded, the suppression propagates so that, for example, an issue in a single definition that is used 100 times doesn't require 100 suppressions (just the 1).
However, there are other kinds of issues, such as where a TypeSpec operation template adds parameters to every operation. This results in many of unique paths that all have to be individually suppressed because the issues are duplicated in the generated Swagger itself.
Should we allow some kind of wildcard mechanism for targeting multiple paths?
The text was updated successfully, but these errors were encountered:
Currently, suppressions only allow you to target a specific path. If that path is then expanded, the suppression propagates so that, for example, an issue in a single definition that is used 100 times doesn't require 100 suppressions (just the 1).
However, there are other kinds of issues, such as where a TypeSpec operation template adds parameters to every operation. This results in many of unique paths that all have to be individually suppressed because the issues are duplicated in the generated Swagger itself.
Should we allow some kind of wildcard mechanism for targeting multiple paths?
The text was updated successfully, but these errors were encountered: