microsoft / microsoft/azure-devops-auth-samples
The managed client console app is not using the client libraries to get project lists
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 277
- Forks
- 307
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 2
Description
Shouldn't this should be using something like...
var vssConnection = new VssConnection(,,,,); // any overload that does not assume the user has a PAT already
var projectClient = _vssConnection.CurrentConnection.GetClient<ProjectHttpClient>();
var projects = await projectClient.GetProjects();
?
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.
Research direction
Start at ManagedClientConsoleAppSample/Program.cs around line 91 and inspect how the project list is currently obtained. Compare it with the proposed VssConnection and ProjectHttpClient approach; done means the managed console sample retrieves projects through the client library without assuming the user already has a PAT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100