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: Ensure loading of parent directory after lower level directories works #851

Merged
merged 2 commits into from
Apr 6, 2022

Conversation

radeksimko
Copy link
Member

Background

Previously if a nested directory/module was opened, kept open, and a parent directory was then opened, that parent directory would fail to load, resulting in file not found errors in the log and causing all IntelliSense for the parent to not be available.

The bug was introduced as part of #771 (i.e. affects 0.26.0+)

Before

2022-04-06 09 47 22

After

2022-04-06 09 46 37

@radeksimko radeksimko added the bug Something isn't working label Apr 6, 2022
@radeksimko radeksimko requested a review from a team April 6, 2022 09:09
@radeksimko radeksimko self-assigned this Apr 6, 2022
@radeksimko radeksimko added this to the v0.27.0 milestone Apr 6, 2022
Copy link
Member

@dbanck dbanck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I'm not able to reproduce the issue with this fix

@github-actions
Copy link

This functionality has been released in v0.27.0 of the language server.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants