No way to find current repository id from code hub
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- api
Research direction
Start by reviewing the code hub extension point and the SDK services listed in CommonServiceIds, then compare what getConfiguration, getPageContext, and getWebContext expose. Done means establishing whether the selected repository ID or name can be provided through an existing or new API, with the behavior documented or covered by an appropriate test.
Written by the indexing model from the issue text.
Description
I'd like to make an extension to help analyze and show information about a repository. Right now I'd like to do it using the code hub extension point.
When I navigate to my hub the current repository is shown in the repository selector at the top of the page. However, I've been unable to find an API method - either directly in the SDK, or in the services listed in CommonServiceIds that will provide the ID or name of the selected repository.
I've also done several searches including searching the issues here, and am unable to find any solution that way either. I did find this issue on the previous repository: https://github.com/microsoft/vss-web-extension-sdk/issues/114 -- But this does not provide a solution. IIt sounded like maybe it would be possible to get this using getConfiguration, getPageContext, or getWebContext, but when I try this they come back empty pageContext has webContext in it, but is otherwise empty).
For me, not having this means probably having my users go without the functionality that I was planning to create an extension for.
Is there some way for me to get this value? Can I somehow make it show up in the result of getPageContext or something like that?
- Dominant language
- TypeScript
- Stars
- 159
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from microsoft/azure-devops-extension-sdk
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
microsoft/azure-devops-extension-sdk#79 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
microsoft/azure-devops-extension-sdk#140 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in microsoft/azure-devops-extension-sdk
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·