mirror of
https://github.com/l0ng-ai/openidea.git
synced 2026-11-19 00:10:00 +00:00
Plugin run configurations could not set environment variables, and Debug only worked when a source file in the arguments let the IDE infer a debugger, so a plugin could run `func start` for an Azure Functions app but not debug the worker it starts. API 1.9 adds the optional `launch-configurations` export, preferred over `run-configurations` when a component has both. Each configuration can add environment variables (only names the IDE's environment doesn't already have, like `process` commands) and name a debugger: launch the program under a language's debugger, or run it and attach to the first process of an Attach to Process kind that the run starts. Only the run's own descendants are candidates; the IDE waits up to a minute while the run lasts and otherwise leaves it running without the debugger. Remote projects resolve the process on the server. The SDK gets `LaunchConfigurations` / `launch_configurations`, the README and docs describe the export, and the bundled components and fixtures are rebuilt for 1.9.
81 lines
2.9 KiB
Plaintext
81 lines
2.9 KiB
Plaintext
package openidea:plugin@1.9.0;
|
|
|
|
/// Optional export (world `plugin-file-actions`): quick fixes and
|
|
/// refactorings that create, rename or delete files, next to the text edits
|
|
/// `providers.code-actions` offers. Declare the `code-actions` provider kind in
|
|
/// `[[contributes.providers]]`; the host calls `code-actions` here with the same
|
|
/// budget and lists the results with the others.
|
|
interface file-actions {
|
|
use types.{error, range, text-edit};
|
|
|
|
/// The document the actions are for (the editor's text while it is open).
|
|
record document {
|
|
/// Absolute path.
|
|
path: string,
|
|
language: string,
|
|
version: u64,
|
|
text: string,
|
|
}
|
|
|
|
/// Text edits to one file.
|
|
record file-edit {
|
|
path: string,
|
|
edits: list<text-edit>,
|
|
}
|
|
|
|
/// A file change, applied before the action's text edits.
|
|
variant file-operation {
|
|
/// Fails when the file exists, unless `overwrite`.
|
|
create(create-file),
|
|
rename(rename-file),
|
|
/// Deletes the file; undoing the action restores it.
|
|
delete(delete-file),
|
|
}
|
|
|
|
/// A new file with its text; missing parent directories are created.
|
|
record create-file {
|
|
path: string,
|
|
text: string,
|
|
overwrite: bool,
|
|
}
|
|
|
|
/// Moves `path` to `new-path`.
|
|
record rename-file {
|
|
path: string,
|
|
new-path: string,
|
|
}
|
|
|
|
/// The file to delete.
|
|
record delete-file {
|
|
path: string,
|
|
}
|
|
|
|
/// A code action that changes files. Paths are absolute or relative to the
|
|
/// project root, and stay inside it: a path outside disables the action.
|
|
record file-action {
|
|
title: string,
|
|
/// `quickfix`, `refactor`, …
|
|
kind: option<string>,
|
|
preferred: bool,
|
|
/// Applied first, in order, as one workspace edit with `edits`: if
|
|
/// any operation or edit fails, nothing is applied, and one undo
|
|
/// reverses all of it.
|
|
operations: list<file-operation>,
|
|
/// Applied after the operations; may target files they create.
|
|
edits: list<file-edit>,
|
|
/// Opened once the action is applied.
|
|
open: option<string>,
|
|
/// The plugin's own reference: with it and no `operations` or `edits`,
|
|
/// they are computed by `resolve` once the user picks the action.
|
|
data: option<string>,
|
|
}
|
|
|
|
/// Actions for `selection`, under the edit-path budget.
|
|
code-actions: func(doc: document, selection: range) -> list<file-action>;
|
|
/// The operations and edits of an action listed with `data` and nothing
|
|
/// to apply, once the user picks it (the command budget applies, not the
|
|
/// editor's 50 ms). The same four prompts as `providers.resolve-code-action`
|
|
/// work here, in the editor's window and excluding the wait from the budget.
|
|
resolve: func(doc: document, action: file-action) -> result<file-action, error>;
|
|
}
|