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

Add a new error code for invalid scenario #297

Merged

Conversation

greenscientist
Copy link
Contributor

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: #295

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
@tahini
Copy link
Collaborator

tahini commented Jun 17, 2024

When you merge, please add an issue in Transition to support this return value

@greenscientist
Copy link
Contributor Author

When you merge, please add an issue in Transition to support this return value

Will do. Transition should never gets this error, so we'll need to make it quite apparent.

@greenscientist greenscientist merged commit 6bde986 into chairemobilite:v2c Jun 17, 2024
5 checks passed
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.

If the client send a wrong scenario, error message should state it so
2 participants