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

Support for Multiple Content Roots #1821

Merged
merged 18 commits into from
Jun 29, 2021
Merged

Support for Multiple Content Roots #1821

merged 18 commits into from
Jun 29, 2021

Conversation

radeusgd
Copy link
Member

@radeusgd radeusgd commented Jun 25, 2021

Pull Request Description

Closes #1780

Important Notes

Checklist

Please include the following checklist in your PR:

  • The documentation has been updated if necessary.
  • All code conforms to the Scala, Java, and Rust style guides.
  • All documentation and configuration conforms to the markdown and YAML style guides.
  • All code has been tested where possible.

@radeusgd radeusgd marked this pull request as ready for review June 25, 2021 18:10
@radeusgd radeusgd self-assigned this Jun 28, 2021
@radeusgd radeusgd added Category: Backend p-high Should be completed in the next sprint labels Jun 28, 2021
Copy link
Contributor

@kustosz kustosz left a comment

Choose a reason for hiding this comment

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

LGTM, but @4e6 should have the final say on this one

@radeusgd radeusgd force-pushed the wip/rw/extend-content-roots branch 2 times, most recently from 31afa9d to befd664 Compare June 29, 2021 09:48
@@ -2235,8 +2176,7 @@ addition of the root in order to inform them of the content root's ID.

```typescript
{
id: UUID; // The content root ID
absolutePath: [String];
root: ContentRoot;
Copy link
Contributor

Choose a reason for hiding this comment

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

Just a reminder to make sure that the appropriate task is scheduled on the IDE side

Copy link
Member Author

Choose a reason for hiding this comment

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

@farmaazon @MichaelMauderer I understand that this will likely need to be integrated for the https://github.com/enso-org/ide/issues/1634
Besides, I understand that before that the file/rootAdded notification was not being handled. Is it a breaking change for the IDE that we will start sending it? Will it cause errrors if you have no handler for it? If yes, I'd like to ask if you can add at least a dummy handler for compatibility which can later be extended to its full functionality.

Copy link
Contributor

@4e6 4e6 left a comment

Choose a reason for hiding this comment

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

Discussed that the root manager doesn't try to access the project directory during the language server startup

@radeusgd radeusgd force-pushed the wip/rw/extend-content-roots branch from befd664 to 67826d2 Compare June 29, 2021 15:50
@radeusgd radeusgd merged commit 0b347d7 into main Jun 29, 2021
@radeusgd radeusgd deleted the wip/rw/extend-content-roots branch June 29, 2021 16:52
iamrecursion pushed a commit that referenced this pull request Jul 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p-high Should be completed in the next sprint
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement Missing Parts of Multiple Content Roots
3 participants