Errors Enum - common parameters for cases
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have got sample Error enum in my application:
public enum APIError: Error
case IncorrectArguments(message: String)
case MissingArgument(message: String)
And error handling looks like:
do
return try next.respond(to: request)
catch let error as APIError
throw Abort(.badRequest, reason: error.message)
But I get compilation error in here saying: Value of type 'APIError' has no member 'message'
.
I know I can get parameters by pattern matching, but I don't want to handle every case in exactly same way:
do
return try next.respond(to: request)
catch APIError.MissingArgument(let message)
throw Abort(.badRequest, reason: message)
catch APIError.IncorrectArguments(let message)
throw Abort(.badRequest, reason: message)
In future there may be more APIErrors in enum and I don't want to handle each one using separate catch block, because everyone will be exactly the same.
Is there any way to handle these errors in some generic way?
swift error-handling
add a comment |
I have got sample Error enum in my application:
public enum APIError: Error
case IncorrectArguments(message: String)
case MissingArgument(message: String)
And error handling looks like:
do
return try next.respond(to: request)
catch let error as APIError
throw Abort(.badRequest, reason: error.message)
But I get compilation error in here saying: Value of type 'APIError' has no member 'message'
.
I know I can get parameters by pattern matching, but I don't want to handle every case in exactly same way:
do
return try next.respond(to: request)
catch APIError.MissingArgument(let message)
throw Abort(.badRequest, reason: message)
catch APIError.IncorrectArguments(let message)
throw Abort(.badRequest, reason: message)
In future there may be more APIErrors in enum and I don't want to handle each one using separate catch block, because everyone will be exactly the same.
Is there any way to handle these errors in some generic way?
swift error-handling
You are throwing errors in catch. You'd want to throw error in a function and catch it in aDo..Catch
– Desdenova
Nov 15 '18 at 14:19
throw Abort
is Vapor way to return response with given status and message.
– Blejwi
Nov 15 '18 at 14:23
@Blejwi check my answer.
– Raul Mantilla
Nov 15 '18 at 17:48
add a comment |
I have got sample Error enum in my application:
public enum APIError: Error
case IncorrectArguments(message: String)
case MissingArgument(message: String)
And error handling looks like:
do
return try next.respond(to: request)
catch let error as APIError
throw Abort(.badRequest, reason: error.message)
But I get compilation error in here saying: Value of type 'APIError' has no member 'message'
.
I know I can get parameters by pattern matching, but I don't want to handle every case in exactly same way:
do
return try next.respond(to: request)
catch APIError.MissingArgument(let message)
throw Abort(.badRequest, reason: message)
catch APIError.IncorrectArguments(let message)
throw Abort(.badRequest, reason: message)
In future there may be more APIErrors in enum and I don't want to handle each one using separate catch block, because everyone will be exactly the same.
Is there any way to handle these errors in some generic way?
swift error-handling
I have got sample Error enum in my application:
public enum APIError: Error
case IncorrectArguments(message: String)
case MissingArgument(message: String)
And error handling looks like:
do
return try next.respond(to: request)
catch let error as APIError
throw Abort(.badRequest, reason: error.message)
But I get compilation error in here saying: Value of type 'APIError' has no member 'message'
.
I know I can get parameters by pattern matching, but I don't want to handle every case in exactly same way:
do
return try next.respond(to: request)
catch APIError.MissingArgument(let message)
throw Abort(.badRequest, reason: message)
catch APIError.IncorrectArguments(let message)
throw Abort(.badRequest, reason: message)
In future there may be more APIErrors in enum and I don't want to handle each one using separate catch block, because everyone will be exactly the same.
Is there any way to handle these errors in some generic way?
swift error-handling
swift error-handling
asked Nov 15 '18 at 14:14
BlejwiBlejwi
390420
390420
You are throwing errors in catch. You'd want to throw error in a function and catch it in aDo..Catch
– Desdenova
Nov 15 '18 at 14:19
throw Abort
is Vapor way to return response with given status and message.
– Blejwi
Nov 15 '18 at 14:23
@Blejwi check my answer.
– Raul Mantilla
Nov 15 '18 at 17:48
add a comment |
You are throwing errors in catch. You'd want to throw error in a function and catch it in aDo..Catch
– Desdenova
Nov 15 '18 at 14:19
throw Abort
is Vapor way to return response with given status and message.
– Blejwi
Nov 15 '18 at 14:23
@Blejwi check my answer.
– Raul Mantilla
Nov 15 '18 at 17:48
You are throwing errors in catch. You'd want to throw error in a function and catch it in a
Do..Catch
– Desdenova
Nov 15 '18 at 14:19
You are throwing errors in catch. You'd want to throw error in a function and catch it in a
Do..Catch
– Desdenova
Nov 15 '18 at 14:19
throw Abort
is Vapor way to return response with given status and message.– Blejwi
Nov 15 '18 at 14:23
throw Abort
is Vapor way to return response with given status and message.– Blejwi
Nov 15 '18 at 14:23
@Blejwi check my answer.
– Raul Mantilla
Nov 15 '18 at 17:48
@Blejwi check my answer.
– Raul Mantilla
Nov 15 '18 at 17:48
add a comment |
1 Answer
1
active
oldest
votes
You can define computed properties on an enum like so:
public enum APIError: Error
case IncorrectArguments(message: String)
case MissingArgument(message: String)
var message: String
switch self
case .IncorrectArguments(let message): return message
case .MissingArgument(let message): return message
And call the message computed properties from your catch clouser like this:
do
return try next.respond(to: request)
catch let error as APIError
throw Abort(.badRequest, reason: error.message)
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53321394%2ferrors-enum-common-parameters-for-cases%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can define computed properties on an enum like so:
public enum APIError: Error
case IncorrectArguments(message: String)
case MissingArgument(message: String)
var message: String
switch self
case .IncorrectArguments(let message): return message
case .MissingArgument(let message): return message
And call the message computed properties from your catch clouser like this:
do
return try next.respond(to: request)
catch let error as APIError
throw Abort(.badRequest, reason: error.message)
add a comment |
You can define computed properties on an enum like so:
public enum APIError: Error
case IncorrectArguments(message: String)
case MissingArgument(message: String)
var message: String
switch self
case .IncorrectArguments(let message): return message
case .MissingArgument(let message): return message
And call the message computed properties from your catch clouser like this:
do
return try next.respond(to: request)
catch let error as APIError
throw Abort(.badRequest, reason: error.message)
add a comment |
You can define computed properties on an enum like so:
public enum APIError: Error
case IncorrectArguments(message: String)
case MissingArgument(message: String)
var message: String
switch self
case .IncorrectArguments(let message): return message
case .MissingArgument(let message): return message
And call the message computed properties from your catch clouser like this:
do
return try next.respond(to: request)
catch let error as APIError
throw Abort(.badRequest, reason: error.message)
You can define computed properties on an enum like so:
public enum APIError: Error
case IncorrectArguments(message: String)
case MissingArgument(message: String)
var message: String
switch self
case .IncorrectArguments(let message): return message
case .MissingArgument(let message): return message
And call the message computed properties from your catch clouser like this:
do
return try next.respond(to: request)
catch let error as APIError
throw Abort(.badRequest, reason: error.message)
edited Nov 15 '18 at 16:05
answered Nov 15 '18 at 15:53
Raul MantillaRaul Mantilla
1395
1395
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53321394%2ferrors-enum-common-parameters-for-cases%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You are throwing errors in catch. You'd want to throw error in a function and catch it in a
Do..Catch
– Desdenova
Nov 15 '18 at 14:19
throw Abort
is Vapor way to return response with given status and message.– Blejwi
Nov 15 '18 at 14:23
@Blejwi check my answer.
– Raul Mantilla
Nov 15 '18 at 17:48