Lorenzo

IMHO we need to consolidate the existing functionalities before getting into improving the developer experience. Please run a double-check (a checklist maybe) about what it is currently usable in hydrus...

Is this something similar to use `before_request` and `after_request` decorators in Flask? Developer can just declare those hooks.

Yes let's keep this with low priority. Logging is fundamental for proper maintenance.

Please close if fixed by merge. Thanks, good one!

I think this can be moved to the parser's repo https://github.com/HTTP-APIs/hydra-openapi-parser/issues

is this going to be merged?

we would like to provide different alternatives for installation, one of which can be `poetry`. ideally the requirements definition should be same between `requirements.txt` and `pyproject.toml`

cc: @ceteri @tomaarsen

yes I would like to remove the current interface. If there are breaking changes, maybe the time for applying them is now, before it stabilises. Anyway we could have both...

we probably want some methods that returns `numpy.array`, I will reuse what it is already there for sure.