Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1061 handle hets api errors #1202

Merged
merged 13 commits into from
Feb 23, 2015
Merged

1061 handle hets api errors #1202

merged 13 commits into from
Feb 23, 2015

Conversation

0robustus1
Copy link
Contributor

Shall partially fix #1061. It provides basic error handling in which the user will actually get the
hets-error message where possible. It however probably requires improvement, which i will do in a later pull-request. But seeing as this seems to be an important issue, we should still review and merge this pull-request.

class ExecutionError < HetsError
attr_reader :abort_execution

def initialize(msg=nil, abort_execution: false)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Style/SpaceAroundEqualsInParameterDefault: Surrounding space missing in default value assignment.

@0robustus1 0robustus1 force-pushed the 1061-handle_hets_api_errors branch 2 times, most recently from 858fdbe to 12da985 Compare February 13, 2015 15:32
This should allow custom error handling for all types of errors that are
not handled by the GetCaller itself.
Descendants should/must provide an implementation
of the perform method, which shall return `false`
if error handling was not possible.
In order to function correctly an error handler
needs the instance of the caller (GetCaller for example).
As the error handler however was supplied when creating
the caller this would create an impossible paradox.
So we'll use a public-setter for now.
This way the method can determine itself whether
error_handling was successful and call the block
if appropriate.
We need the improved error-handling of
hets for clif ontologies in the API.
When we access the path we will get a version that
still contains percent-escapes, we'll need to unescape
them to do the iri-check.
@eugenk
Copy link
Member

eugenk commented Feb 23, 2015

👍

0robustus1 added a commit that referenced this pull request Feb 23, 2015
@0robustus1 0robustus1 merged commit 5423245 into staging Feb 23, 2015
@0robustus1 0robustus1 deleted the 1061-handle_hets_api_errors branch February 23, 2015 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Handling of hets-errors in API
3 participants