Skip to content

chore(eslint): Enable no-relative-import-paths as an error #89339

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

Merged
merged 6 commits into from
Apr 14, 2025

Conversation

ryan953
Copy link
Member

@ryan953 ryan953 commented Apr 10, 2025

This rule was added in #89333 as a warning. Warning gives folks a chance to update and avoid conflicts/CI failures

#89334 went ahead and fixed everything.

And now we're setting the rule to be an error. Before merging we'll want to merge master and re-run the linter to catch anything new or missed.

@ryan953 ryan953 requested a review from a team as a code owner April 10, 2025 20:21
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Apr 10, 2025
@ryan953 ryan953 requested review from a team as code owners April 14, 2025 21:07
@ryan953 ryan953 requested review from a team and removed request for a team April 14, 2025 21:07
@ryan953 ryan953 requested a review from a team as a code owner April 14, 2025 21:58
@ryan953 ryan953 merged commit 20eca7b into master Apr 14, 2025
41 checks passed
@ryan953 ryan953 deleted the ryan953/eslint-no-relative-import-paths-error branch April 14, 2025 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants