chore: enforce vscode import preference in settings #2008
Merged
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
keellyp
force-pushed
the
vscode-import
branch
from
901082c to
98cd45f
Compare
keellyp
force-pushed
the
vscode-import
branch
from
98cd45f to
80b3e8c
Compare
ansmonjol
approved these changes
Jan 30, 2025
stephenlago99
approved these changes
Jan 30, 2025
keellyp
force-pushed
the
vscode-import
branch
from
80b3e8c to
4d1f5c4
Compare
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.
Context
Enforce consistency in the code using vscode preferences
Description
In order to avoid both relative and non-relative import type, let's add a rule in the vscode settings to prevent importing files relatively.