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.

Sign up for GitHub

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

Jump to bottom

If the client send a wrong scenario, error message should state it so #295

Closed
greenscientist opened this issue Jun 11, 2024 · 0 comments · Fixed by #297
Closed

If the client send a wrong scenario, error message should state it so #295

greenscientist opened this issue Jun 11, 2024 · 0 comments · Fixed by #297

Comments

@greenscientist
Copy link
Contributor

Currently, if we send a wrong scenario ID, we get a MISSING_PARAM_SCENARIO,
{'status': 'query_error', 'errorCode': 'MISSING_PARAM_SCENARIO'}

Instead of a message stating that the scenario was there but wrong.
greenscientist added a commit to greenscientist/trRouting that referenced this issue Jun 12, 2024
@greenscientist
Add a new error code for invalid scenario
b832f7a 
Currently, if we send a scenario id but that ID is not in the available cache data,
we return the error MISSING_SCENARIO, which is missleading.

We add a new error code INVALID_SCENARIO, that will be returned if the scenario_id
is not a valid uuid, or it's not present in our data source

Fixes: chairemobilite#295
@greenscientist greenscientist mentioned this issue Jun 12, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a new error code for invalid scenario greenscientist/trRouting
1 participant
@greenscientist