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

Implement custom datatype for common extractions #29

Closed
bbangert opened this issue Sep 19, 2018 · 0 comments
Closed

Implement custom datatype for common extractions #29

bbangert opened this issue Sep 19, 2018 · 0 comments

Comments

@bbangert
Copy link
Member

A lot of boiler-plate exists for the handlers as they frequently require at leas 3 different extractors. This can be done in a single object for a cleaner API with less boilerplate with its own extractor.

@bbangert bbangert added the next label Sep 19, 2018
bbangert added a commit that referenced this issue Oct 1, 2018
As Spanner needs a different identifier, this introduces a HawkIdentifer
object that will provide a NoSql compatible random string identifier for
users as well as a legacy compatible identifier for testing.

Issue #29
bbangert added a commit that referenced this issue Oct 4, 2018
Add's a variety of validation machinery to handle validation errors and
their coercion to appropriate JSON actix-web errors that match the
format of the Cornice error JSON from the Python version.

Closes #29
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

No branches or pull requests

1 participant