Repository navigation
Fix: Extract workspace description from nested API response - #12
Closed
DJKampouris wants to merge 2 commits into
Closed
DJKampouris wants to merge 2 commits into
DJKampouris wants to merge 2 commits into
Conversation
The `invoke_api` utility nests the REST payload under a 'response' key. Previously, the description was incorrectly accessed from the top-level API envelope, leading to `None` values and preventing proper workspace identification.
Prevents temporary files generated by development tooling from being tracked and committed.
Author
|
Will do a new PR when ready. |
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.
The
invoke_apiutility nests the REST payload under a 'response' key.Previously, the description was incorrectly accessed from the top-level
API envelope, leading to
Nonevalues and preventing proper workspaceidentification.