ActionProvider & its Lookup consolidation in VSCode extension #7105
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Third attempt to integrate
ActionProvider
and itsLookup
improvements needed by enso-org/enso#9041. #7011 got merged with failing tests and reverted. #7059 was targeted fordelivery
branch, but that one has been deleted already.java.mx.projects
for behavior implemented by Update the mx suite parsing to work with sources of GraalVM version 23.1.0 #7013createTargetLookup
method and uses it forisEnabled
check as well asinvokeAction
(I believe)FileObject
&DataObject
to the lookup even when working on the whole Project - that's the change which fixes problems we face in EnsoPer discussion in #7059 the
Project
instance is included in thecreateTargetLookup
, but not the content ofProject.getLookup()
.