We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In some cases, we don't want the log output of a lower priority issue to bother us.
We planning add a new annotation @SuppressFiesta to disable log output in some cases.
@SuppressFiesta
e.g.:
If you have annotated on a class, and you use the class in the other place, usually there will be a output:
@Dangerous("You are using the DangerousClass!") public class DangerousClass { } public void doSomething() { DangerousClass danger = // do something... }
Output will be like:
SomeClass.java:[1,1] Dangerous: You are using the DangerousClass!
With the new @SuppressFiesta annotation, we could disable the output in this way:
@SuppressFiesta(Dangerous.class) public void doSomething() { DangerousClass danger = // do something... }
Further, we could using the SuppressWarnings annotation that defined in Java, like @SuppressWarnings("FiestaDanger") to disable the output.
SuppressWarnings
@SuppressWarnings("FiestaDanger")
The text was updated successfully, but these errors were encountered:
roll-w
When branches are created from issues, their pull requests are automatically linked.
In some cases, we don't want the log output of a lower priority issue to bother us.
We planning add a new annotation
@SuppressFiesta
to disable log output in some cases.e.g.:
If you have annotated on a class, and you use the class in the other place, usually there will be a output:
Output will be like:
With the new
@SuppressFiesta
annotation, we could disable the output in this way:Further, we could using the
SuppressWarnings
annotation that defined in Java, like@SuppressWarnings("FiestaDanger")
to disable the output.The text was updated successfully, but these errors were encountered: