Closed sutterj closed 2 months ago
Currently there is some handling in the create procedure to make a "pretty" message if one already exists:
This is the only error that has this, so is it worthwhile to do this for the other procedures or is that too specific/tedious because of the number of possible errors:
Currently there is some handling in the create procedure to make a "pretty" message if one already exists:
This is the only error that has this, so is it worthwhile to do this for the other procedures or is that too specific/tedious because of the number of possible errors:
@ahpook thoughts?
Hmmm. How many potential other messages are we looking at? The json barf is pretty ugly ...
Is the format predictable enough to extract the message
field and pretty-print that with a generic "Failed to create mirror. Error was:
I'm not really sure how many, but I would guess that the name conflict one is probably the most common and that one is already covered. I would imagine that the API is consistent and returns a message field though and that would be easy to add to the banner by itself.
Pull Request
Proposed Changes
Readiness Checklist
Author/Contributor
npm run lint
and fix any linting issues that have been introducednpm run test
and run tests@jeffrey-luszcz
Reviewer
bug
,documentation
,enhancement
,infrastructure
,maintenance
, orbreaking