Repository navigation
feat: add the tooling component for editor language support - #13
Merged
Merged
Conversation
NenkaLab
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
A fourth plugin component, tooling, lets a plugin help the editor understand a language: diagnostics, completion, hover and signature help over the text the host sends. It runs no scripts and is not part of a project's configuration.
LanguageTools,ToolingFactory,ToolingContext,ToolingHost(read-only access to files the host allows) and the data types incontract/tooling.ToolingEndpoint(plugin side) andRemoteLanguageTools(host side) over the existingRpcPeer. Calls arrive on one thread in order, and questions the host has given up on are skipped. Configuring may take a longersetupTimeoutMs, since a tooling often loads its compiler there.PluginService.tooling,PluginRole.TOOLINGand<tooling languages>in the manifest.ToolingHarnessandToolingConformance. Readme section.No AIDL change, so
BinderContract.VERSIONand the protocol version stay as they are.Test plan
:contract:test(newToolingSessionTest, 11 cases),:android:testDebugUnitTest,:tck:test.