microsoft / microsoft/debug-adapter-protocol
Make hot reload a standard request
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 173
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 2
Description
Within the Dart extension, we use a custom request to ask our running application to update source code files that have changed (see https://github.com/Dart-Code/Dart-Code/blob/master/src/extension/dart/hot_reload_save_handler.ts#L116). We’re wondering if this could be made into a standard event type, e.g.:
interface HotReloadRequest extends Request {
command: 'hotReload';
arguments: HotReloadArguments;
}
interface HotReloadArguments {
/** This describes how the hot reload was triggered, e.g. manual request vs automatically on save */
reason: string;
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the hot-reload request usage in src/extension/dart/hot_reload_save_handler.ts at line 116, then review the Debug Adapter Protocol request definitions. Determine how the proposed hotReload request and its reason argument fit the protocol, and confirm that the standard request can represent both manual and automatic-on-save reloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100