Go over exported API in azure core and arm libraries
Open
design:needed
eng
triaged:core
- Dominant language
- TypeScript
- Stars
- 27
- Forks
- 90
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 156
Description
Make sure we only export what should be used and no internal iterms
Contributor guide
Research direction
Start by locating the Azure Core and ARM library entry points and inventorying their exported symbols against the intended public surface. Determine which exports are internal; completion means the libraries expose only the APIs intended for use, with checks covering the resulting export surface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100