microsoft / microsoft/react-native-windows
Generate intellisense docs out of the same content as WinRT API docs
Open
Nobody has claimed this yet.
Area: Developer Experience
enhancement
PR Follow-up
Workstream: Developer Experience
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
ensure we are also generating intellisense docs out of the same content
Originally posted by @asklar in https://github.com/microsoft/react-native-windows/issues/6509#issuecomment-728276936
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 by locating the existing WinRT API documentation generation described in the issue and trace where its source content is produced. Determine how IntelliSense documentation is currently generated, if at all. Done means IntelliSense documentation is generated from the same content as the WinRT API docs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100