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

Manage errors in analysis operations #21

Open
AML14 opened this issue Jan 3, 2020 · 0 comments
Open

Manage errors in analysis operations #21

AML14 opened this issue Jan 3, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@AML14
Copy link
Collaborator

AML14 commented Jan 3, 2020

Right now, errors are not managed inside analysis operations.

  • Example 1: When "isDeadParameter" receives a parameter which doesn't exist, it returns "true" as output, i.e. as if the (nonexistent) parameter was dead.
  • Example 2: When "isFalseOptional" receives a parameter which doesn't exist, an exception occurs, therefore the program exits.
  • Example 3: When "isValidRequest" receives parameters which don't exist, an empty map is returned, as if the requestwas invalid. (Although this may be considered the right behaviour...).

These behaviours should be managed differently, for example, returning null in those cases or throwing an expected Exception.

@AML14 AML14 added the enhancement New feature or request label Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant