Skip to content

Repair rubocop refusing to run (#97)#262

Open
sinfomicien wants to merge 1 commit into
chef:mainfrom
sinfomicien:update-and-repair-extension
Open

Repair rubocop refusing to run (#97)#262
sinfomicien wants to merge 1 commit into
chef:mainfrom
sinfomicien:update-and-repair-extension

Conversation

@sinfomicien
Copy link
Copy Markdown

@sinfomicien sinfomicien commented Apr 7, 2025

Description

As i start to look into the problem, got multiples problem to handle. So i tried to correct them all:

  • Upgrade dependencies
  • Use ESlint instead of TSLint(obsolete)
  • Remove a null token parameter in findFiles call, generating extension load error
  • Replace rootPath (deprecated) by workspaceFolders[0].uri.fsPath
  • Correct a language/snippet file loading problem(berkshelf vs berkfile) (Extension issue #142)
  • added shell: true in spawn execution, it was failing without with node 20.
  • Removed test from node 15 (unsupported)
  • Adding test for node 18 and node 20.
  • Change gif image URL in README (master branch is now main)
  • Escape $ from some snippet description to avoid warning in VSCode

Now, all problems are correctly highlighted (even if for now, it’s not possible to correct them automatically).

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

@sinfomicien sinfomicien requested review from a team as code owners April 7, 2025 12:59
@sinfomicien sinfomicien force-pushed the update-and-repair-extension branch from e89f937 to 3519ab6 Compare April 7, 2025 13:04
@sinfomicien sinfomicien mentioned this pull request Apr 7, 2025
@sinfomicien sinfomicien force-pushed the update-and-repair-extension branch from 3519ab6 to 6d617ee Compare April 7, 2025 13:08
@sinfomicien sinfomicien force-pushed the update-and-repair-extension branch from 6d617ee to 7402d95 Compare April 7, 2025 13:16
@sinfomicien sinfomicien requested a review from a team as a code owner April 7, 2025 13:16
- Upgrade dependencies
- Use ESlint instead of TSLint(obsolete)
- Remove a null token parameter in findFiles call, generating extension load error
- Replace rootPath (deprecated) by workspaceFolders[0].uri.fsPath
- Correct a language/snippet file loading problem(berkshelf vs berkfile) (chef#142)
- Correct gif image url in README (master branch now is main)
- Escape $ in some snippet description to avoid warning from VSCode

Signed-off-by: Nicolas Blanc <sinfomicien@gmail.com>
@sinfomicien sinfomicien force-pushed the update-and-repair-extension branch from 7402d95 to 260aa8c Compare April 7, 2025 14:50
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Apr 7, 2025

@sinfomicien
Copy link
Copy Markdown
Author

@clintoncwolfe , is it possible to review this PR ? Could it be merged at some point ?

@sinfomicien
Copy link
Copy Markdown
Author

@nikhil2611 could you review the PR please ?

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.

1 participant