Fix Angular import warning and enable lint rule to prevent regressions#2848
Merged
Fix Angular import warning and enable lint rule to prevent regressions#2848
Conversation
1 task
jattasNI
changed the title
rajsite
approved these changes
Feb 3, 2026
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
2 participants
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.
Pull Request
🤨 Rationale
Fixes #2845 and addresses warnings introduced by #2835 and described in this comment on that PR.
👩💻 Implementation
Enable the @typescript-eslint/no-import-type-side-effects lint rule.
Fix the violations including the one I introduced in spright chat plus some other pre-existing ones.
🧪 Testing
Inspected build output and warnings are now gone. Lint is now passing after addressing the violations.
✅ Checklist