Fix eslint warnings #116
Merged
Fix eslint warnings #116
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
charlieegan3
approved these changes
Apr 2, 2024
|
Seeing all we do is a DCO check here, I'll try and get this into a workflow step too before we merge this. |
And ignore some of the most noisy ones for now. Should fix these later obviously, but for now I was mainly just concerned with fixing the "are you sure you want to continue despite the errors reported" warning that would be shown each time one started a debugging session. Signed-off-by: Anders Eknert <[email protected]>
anderseknert
force-pushed
the
eslint-compliance
branch
from
39f03b0
to
c00561e
Compare
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
And ignore some of the most noisy ones for now. Should fix these later obviously, but for now I was mainly just concerned with fixing the "are you sure you want to continue despite the errors reported" warning that would be shown each time one started a debugging session.