Skip to content
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

fix(linter): ensure target project locator is not using stale graph in IDE #16534

Merged
merged 1 commit into from
Apr 25, 2023

Conversation

meeroslav
Copy link
Contributor

Current Behavior

Despite project graph, and root mappings being generated fresh in IDE on every change, the rule uses stale target project locator

Expected Behavior

The target project locator should be recreated every time the graph is changed.

Related Issue(s)

Fixes #

@meeroslav meeroslav self-assigned this Apr 25, 2023
@vercel
Copy link

vercel bot commented Apr 25, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nx-dev ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 25, 2023 9:24pm

@meeroslav meeroslav force-pushed the fix-stale-target-project-locator branch from a89f1ad to 866c476 Compare April 25, 2023 21:13
@meeroslav meeroslav enabled auto-merge (squash) April 25, 2023 21:15
@meeroslav meeroslav changed the title fix(linter): ensure target project locator is using stale graph in IDE fix(linter): ensure target project locator is not using stale graph in IDE Apr 25, 2023
@meeroslav meeroslav merged commit d47df3d into nrwl:master Apr 25, 2023
@github-actions
Copy link

github-actions bot commented May 1, 2023

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants