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

Issue #338: Removing problematic console.log. #339

Merged
merged 3 commits into from
Dec 7, 2023

Conversation

davidfmatheson
Copy link
Contributor

Fixes

Issue #338

Proposed Changes

Remove the console.log statement. There is already a debug statement with the same information.

@stevenh
Copy link
Collaborator

stevenh commented Dec 6, 2023

Thanks for this, that would be me missing a clean up, when working against the bug in vscode and debug.

Looks like you just need to rebase to address the update check.

The Windows test run is flaky ATM as it seem to hang right at the end, so don't worry about that one.

@nvuillam
Copy link
Owner

nvuillam commented Dec 6, 2023

You probably also ned to run npm run build :)

Copy link
Owner

@nvuillam nvuillam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR :)

@nvuillam nvuillam merged commit 9fd6584 into nvuillam:main Dec 7, 2023
6 checks passed
@nvuillam
Copy link
Owner

nvuillam commented Dec 7, 2023

@davidfmatheson released in https://github.com/nvuillam/npm-groovy-lint/releases/tag/v13.0.2 , many thanks for your contribution :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants