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

Virtual Component Groups in the Hierarchical Action List (2/2) #3510

Merged
merged 222 commits into from
Jun 15, 2022

Conversation

akavel
Copy link
Contributor

@akavel akavel commented Jun 3, 2022

Pull Request Description

Put information about Virtual Component Groups in the Hierarchical Actions List.

https://www.pivotaltracker.com/story/show/181865548

Important Notes

  • This PR implements the subtask 2 of 2 in the "Virtual Component Groups in the Hierarchical Action List" task.
  • Note: the PR description does not include a screencast due to the changes in this PR not having any visual effect at this moment. The result of this PR's changes would be only observed in the Component Browser, but the Component Browser is not merged yet. As described in the task's Acceptance Criteria, the changes in this PR are currently only covered by tests.
  • Manual integration testing with the Engine showed that a response to an executionContext/getComponentGroups request is non-empty only after an executionContext/executionComplete message is received by the IDE. (See also a discussion on Discord.) This was not known by the IDE team or documented before, and the existing code was modified to take this into account. The protocol docs are expected to be updated by the Engine team.
  • A list of component groups looked up in the suggestion database is cached in the node searcher as an optimization.

[ci no changelog needed]

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 code has been tested:
    • Unit tests have been written where possible.
    • If GUI codebase was changed: Enso GUI was tested when built using BOTH
      ./run ide dist and ./run ide watch.

@akavel akavel requested a review from wdanilo June 13, 2022 10:50
@wdanilo
Copy link
Member

wdanilo commented Jun 14, 2022

I did not check the logic. If @farmaazon is OK with it, we can merge it :)

@akavel
Copy link
Contributor Author

akavel commented Jun 14, 2022

(Process note: the code-review is now Approved, therefore the PR is waiting for an Acceptance/QA Review by @farmaazon on Task https://www.pivotaltracker.com/story/show/181865548 before merge.)

@akavel akavel added the CI: Ready to merge This PR is eligible for automatic merge label Jun 15, 2022
@mergify mergify bot merged commit 0c8b1a1 into develop Jun 15, 2022
@mergify mergify bot deleted the wip/akavel/favorites-in-hal-181865548 branch June 15, 2022 09:47
farmaazon pushed a commit that referenced this pull request Jun 17, 2022
Put information about Virtual Component Groups in the Hierarchical Actions List.

https://www.pivotaltracker.com/story/show/181865548

- This PR implements the subtask 2 of 2 in the ["Virtual Component Groups in the Hierarchical Action List" task](https://www.pivotaltracker.com/story/show/181865548).
- Note: the PR description does not include a screencast due to the changes in this PR not having any visual effect at this moment. The result of this PR's changes would be only observed in the Component Browser, but the Component Browser is not merged yet. As described in the task's Acceptance Criteria, the changes in this PR are currently only covered by tests.
- Manual integration testing with the Engine showed that a response to an `executionContext/getComponentGroups` request is non-empty only after an `executionContext/executionComplete` message is received by the IDE. (See also [a discussion on Discord](https://discord.com/channels/401396655599124480/983669600854106112).) This was not known by the IDE team or documented before, and the existing code was modified to take this into account. The protocol docs are expected to be updated by the Engine team.
- A list of component groups looked up in the suggestion database is cached in the node searcher as an optimization.

[ci no changelog needed]
kazcw pushed a commit that referenced this pull request Jun 29, 2022
Put information about Virtual Component Groups in the Hierarchical Actions List.

https://www.pivotaltracker.com/story/show/181865548

# Important Notes
- This PR implements the subtask 2 of 2 in the ["Virtual Component Groups in the Hierarchical Action List" task](https://www.pivotaltracker.com/story/show/181865548).
- Note: the PR description does not include a screencast due to the changes in this PR not having any visual effect at this moment. The result of this PR's changes would be only observed in the Component Browser, but the Component Browser is not merged yet. As described in the task's Acceptance Criteria, the changes in this PR are currently only covered by tests.
- Manual integration testing with the Engine showed that a response to an `executionContext/getComponentGroups` request is non-empty only after an `executionContext/executionComplete` message is received by the IDE. (See also [a discussion on Discord](https://discord.com/channels/401396655599124480/983669600854106112).) This was not known by the IDE team or documented before, and the existing code was modified to take this into account. The protocol docs are expected to be updated by the Engine team.
- A list of component groups looked up in the suggestion database is cached in the node searcher as an optimization.

[ci no changelog needed]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: Ready to merge This PR is eligible for automatic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants