[APIView] Ensure all language parsers emit CrossLanguagePackageId consistently
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 144
Description
| Parser | CrossLanguagePackageId Support | Issue | Notes |
|--------|-------------------------------|--------|-------|
| TypeSpec | ✅ Supported | Done | Already supported |
| Python | ✅ Supported | Done | Already supported |
| JavaScript| ⚠️ In progress | https://github.com/Azure/azure-sdk-tools/issues/14023 | Add more data and update pipeline |
| Java | ⚠️ In progress | https://github.com/Azure/azure-sdk-tools/issues/14024 | Fix matching and pass more info |
| C# (.NET) | ❌ Not started | https://github.com/Azure/azure-sdk-tools/issues/14096 | Not started |
| Go | ❌ Not started| | Not started |
| Swift | ❓ Unknown | | Needs investigation, no initial phase |
| Rust | ❓ Unknown | | Needs investigation, no initial phase |
| C++ | ❓ Unknown | | Needs investigation, no initial phase |
Contributor guide
Research direction
No files, tests, or entry points are named. Start by investigating how each listed language parser handles CrossLanguagePackageId, using the linked JavaScript, Java, and C# issues as context. Done means determining the status of Swift, Rust, and C++, and ensuring every parser emits the identifier consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, csharp, go, java, javascript, python, rust, swift
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100