at-return-output #63
No reviewers
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Activity:Doing
Activity:Proposal
Runner
AT
Runner
CLI
Runner
HTTP
cleanup
devops
easypeasy
exchange
l8ter
legacy
optimization
privilege
refactor
smell
support
tooling
ux
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: urdt/ussd#63
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "at-return-output"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Updated the code to only show output if the http response code is 200
From the AT documentation:
Based on this, I see it best to return an error response instead of having a success response of 200, leading to an empty result if the menu encountered any errors
Add a test please?
at-return-outputto WIP: at-return-outputThis has been done
I have also moved the mocks package for easier usage
WIP: at-return-outputto at-return-outputVery nice, great efforts on the mocking.
I haven't independently verified that it addresses the issue with the 500, but taking your word that it does.
I have verified that tests run and that it builds.
And that coverage after this PR is nearly 90%