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

Optional API values are not considered correctly #37

Open
mpgirro opened this issue Jan 3, 2019 · 0 comments
Open

Optional API values are not considered correctly #37

mpgirro opened this issue Jan 3, 2019 · 0 comments
Labels
api This issue concerns the API server codebase bug Something isn't working engine This issue concerns the engine library codebase

Comments

@mpgirro
Copy link
Owner

mpgirro commented Jan 3, 2019

If optional values to the REST API are omitted or different parameters are provided, the method parameters in Play result in Nothing incarcerations. For all Nothing values, default values should be used (I think the Engine currently makes sure of this).

However, the API then returns empty result lists. This is not expected behaviour. As of now, it is unsure if the issue is with the Engine or the API.
@mpgirro mpgirro added bug Something isn't working engine This issue concerns the engine library codebase api This issue concerns the API server codebase labels Jan 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api This issue concerns the API server codebase bug Something isn't working engine This issue concerns the engine library codebase
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mpgirro