microsoft / microsoft/terminal
[DefApp] Document how it works
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
@miniksa and @cinnamon-msft to document how this works.
_Originally posted by @miniksa in https://github.com/microsoft/terminal/pull/7489
```[tasklist]
### Tasks
- [ ] Document how the app extension goo works
- [ ] document the com server interface
- [ ] probably add a way to do defterm unpackaged as well
```
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 original discussion in pull request 7489 and trace the DefApp-related implementation from there. The task list calls for documentation of the app extension mechanism and COM server interface, plus consideration of unpackaged defterm support; no files or tests are named, so completion criteria need clarification before work begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100