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

Stricter parameters check in APICall #2

Open
efrecon opened this issue Mar 19, 2018 · 0 comments
Open

Stricter parameters check in APICall #2

efrecon opened this issue Mar 19, 2018 · 0 comments
Assignees
@efrecon
Labels
enhancement

Comments

@efrecon
Copy link
Owner

efrecon commented Mar 19, 2018

Improve APICall implementation so it is able to perform some stricter check on the parameters that are allowed for a given query. This includes:

  • Force presence of parameters that are mandatory
  • Check against "enums" or similar.
  • Check against type
  • Make specific difference between query parameters and headers
  • Keep current heuristics as a fail-over for parameters that have no specification by default
  • Arrange to be able to turn off the previous behaviour for strict compliance (perhaps a connection-wide parameter?)
@efrecon efrecon self-assigned this Mar 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@efrecon efrecon

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@efrecon