Repository navigation
ADO Lens 0.8.1 - #13
Merged
Merged
Conversation
Fixes from testing on a real project. - `adolens` works in any new terminal after an install or upgrade with the script (`get.ps1`, `install.ps1`, `adolens upgrade --install` on such an installation) too: the program folder is added to the user's PATH, as the setup EXE already did; `uninstall.ps1` takes it off. - Tool arguments in another JSON shape are read instead of failing with a bare "An error occurred invoking": `ids=714800` (a number for text), `workItems=[1,2]`, `file=1`, `top="20"`, `draft="true"`. This was behind the failing `ado_update` (even with only a comment), `ado_pr_update action=create` with work items and `ado_attachments file=<n>`. An argument that still cannot be read says which and why. - `ado_attachments`: two files with the same name are listed by number to pick one. - `ado_file history=true`: full commit ids (they work in `ado_changes` and `ado_file version=`), changes that came in with a merge are listed too, and the branch read is named. - `ado_file` without a version names the branch it read (the default one). - `ado_sprint`: a sprint over the Azure DevOps limit of 20 000 work items says so instead of a raw server error; with no current sprint the answer starts with NO CURRENT SPRINT; items in a state this project's process does not know (e.g. from another project) are put in done / in progress by the state's usual name.
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
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.
Fixes from testing on a real project.
adolensworks in any new terminal after an install or upgrade with the script (get.ps1,install.ps1,adolens upgrade --installon such an installation) too: the program folder is added to the user's PATH, as thesetup EXE already did;
uninstall.ps1takes it off.Tool arguments in another JSON shape are read instead of failing with a bare "An error occurred invoking":
ids=714800(a number for text),workItems=[1,2],file=1,top="20",draft="true". This was behind the failingado_update(even with only a comment),ado_pr_update action=createwith work items andado_attachments file=<n>.An argument that still cannot be read says which and why.
ado_attachments: two files with the same name are listed by number to pick one.ado_file history=true: full commit ids (they work inado_changesandado_file version=), changes that came inwith a merge are listed too, and the branch read is named.
ado_filewithout a version names the branch it read (the default one).ado_sprint: a sprint over the Azure DevOps limit of 20 000 work items says so instead of a raw server error; withno current sprint the answer starts with NO CURRENT SPRINT; items in a state this project's process does not know
(e.g. from another project) are put in done / in progress by the state's usual name.