Consistently use Error::NotAvailable instead of Unsupported #349
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.
This PR switches most uses of
Error::Unsupported
toError::NotAvailable
, and translates both toFastlyStatus::Unsupported
.Unsupported
is meant to express things that are not supported by the platform, for example trying to make a request with "HTTP/4".NotAvailable
is meant to express things that are not available or unimplemented in Viceroy.Previously,
Unsupported
would returnFastlyStatus::Unsupported
andNotAvailable
would return the genericFastlyStatus::Error
. This led to a bad user experience for theNotAvailable
case, as the user would see an opaque and generic "Error" message rather than indicating an operation was "Unsupported".This PR (1) changes
Error::NotAvailable
to map toFastlyStatus::Unsupported
and (2) changes all our uses ofError::Unsupported
for things that are not implemented in Viceroy to beError::NotAvailable
.