Lorenzo

Yeah with data I mean instances/objects that are actually served by the interface (the one we store using the PUT method on the `Items` endpoint). > But we would need...

this is something needed @sameshl , also ping @vedangj044 as I think he is working on it

Everything about the code is in the code. For now we only use file database as SQLite. Ask your colleagues in Slack for generic directions.

`hydrus` shall be alway lowercase

please try to run the server in local and see if there is something useful you can add to the document, at this point there are only minor changes in...

you can see the full Travis log at https://app.travis-ci.com/github/HTTP-APIs/hydrus/jobs/557575062 nice try but it is still minor changes. Conventions: * correct spell is "Hydra" for the framework * correct spell is...

> Conventions: > correct spell is "Hydra" for the framework > correct spell is "hydrus" for the server this is still not implemented. Also you have to rebase this PR...

> > Also you have to rebase this PR to the develop branch > > my branch is already on develop >  > yes but your develop is not...

> @Mec-iS I can work on this if you aren't sorry for the late reply. You don't need to ask for permission. You can just follow the Github Flow and...

Are you talking about a Falcon/Flask-like pre_request and post_response hooks? This can be done programmatically using the Flask interface.