feat(get): richer detail view with description and opt-in comments - #27
Merged
Conversation
- Fix the browser URL: build it from org + project name instead of a fragile string-replace on the API url (which left the raw JSON endpoint). - Show area, iteration, tags, parent, reason and the HTML-stripped description. - Add --comments (long-only) to also fetch the discussion via the work item comments API, best-effort so a failure never breaks 'get'. Comments are opt-in to keep the extra API call off the default path; blank line between each. - --output json/csv modes are unchanged (flat field projection). Adds ActionHelpers.WorkItemUrl and HtmlToText with unit tests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Richer
getdetail viewEnhances
devops getwith more context and a working link.Changes
url(_apis/wit/workitems->_workitems/edit), which failed because the API returnsworkItems(capital I) and the project GUID — leaving the raw JSON endpoint. It is now built from the configured org + project name and opens the item directly.--comments(long-only) fetches and shows the discussion via the work item comments API. It is opt-in to keep the extra (preview) API call off the default path, and best-effort — a failure never breaksget. Comments are separated by a blank line.--output json/csvis unchanged (flat field projection).Adds
ActionHelpers.WorkItemUrlandHtmlToTextwith unit tests (72 total).