Skip to content
New issue

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

Suppress unexpected console statement warnings #2003

Closed
ckcherry23 opened this issue May 10, 2023 · 0 comments · Fixed by #2088
Closed

Suppress unexpected console statement warnings #2003

ckcherry23 opened this issue May 10, 2023 · 0 comments · Fixed by #2088

Comments

@ckcherry23
Copy link
Member

What feature(s) would you like to see in RepoSense

Suppress the Unexpected console statement warnings from the CI builds that appear at the end of the Files changed tab due to the console.error() statement in c-summary-charts.vue.

Screenshot 2023-05-10 at 1 36 38 PM

Source: https://github.com/reposense/RepoSense/pull/1999/files

Is the feature request related to a problem?

Multiple warnings from this intentional statement may cause an undesirable warning to be disregarded due to the large warning count.

If possible, describe the solution

Use a comment to disable ESLint warnings for the particular line that is causing the issue.

If applicable, describe alternatives you've considered

All warnings can also be disabled, but this may cause other unintentional issues to be overlooked.

Additional context

Discussed in #1976

@ckcherry23 ckcherry23 changed the title Suppress console statement warnings Suppress unexpected console statement warnings May 10, 2023
@sopa301 sopa301 self-assigned this Jan 21, 2024
ckcherry23 pushed a commit that referenced this issue Jan 26, 2024
Suppress unexpected console warning

A theoretically unreachable console.error() statement has raised a
warning from CI builds. Multiple warnings from this intentional
statement may cause an undesirable warning to be disregarded due to the
large warning count.

Let's suppress this particular warning.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Closed/Completed
Development

Successfully merging a pull request may close this issue.

2 participants