[FIX]: fix analyzer config and TypeScript workspace warnings#396
Open
LLEGIT wants to merge 1 commit into
Open
Conversation
LLEGIT
force-pushed
the
fix/NO-ISSUE/analyzer-config-typescript-workspace
branch
from
f4c86c7 to
7811246
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
corrected the main analyzer’s DevOps env var reference, cleaned up the declaration tsconfig layout in the BFF and main analyzer, removed the deprecated downlevelIteration flag from the affected package tsconfigs, and added analyzer ESLint tsconfigRootDir handling so the monorepo file stopped tripping the parser warning. I also added a workspace ESLint setting for auto-working directories. pnpm lint completed successfully.