Eshaan Bansal

Ability to store metadata/settings as part of Client <-> User relationship

1

There can be use cases where developers wish to store settings/metadata about a user specific to a client. (For example, theme name, styling, avatar, display name, etc.) Few initial implementation...

Create ClientSerializer and ClientViewSet

1

Create a `ClientSerializer` and a corresponding `ClientViewset` for the `Client` model.

https://docs.djangoproject.com/en/3.1/howto/custom-management-commands/

At the moment, the `durin/models.py` is omitted from code coverage, I'd like to change this. - [ ] Include test cases for both models, `AuthToken` and `Client`. - [ ]...

Fixes #7: Shell2HTTP is now a subclass of Flask.Blueprint

1

- [x] Make `Shell2HTTP` a subclass of `Flask.Blueprint` class and related fixes. - [ ] Update examples - [ ] Update tests - [ ] Update docs

Currently, flask-shell2http works just like any other flask extension; you create an object from a class to which you pass the flask application instance. We could follow a different approach...

Fails if ran with multiple gunicorn workers

1

> I figured out that the issue has to do with having multiple Gunicorn workers handling requests. The report only exists for the same worker that handled the original request....

When using `&wait=true`, the `callback_fn` cannot be used to modify the result because it is called _after_ the future completes. This happens if one calls `future.done()` to wait before the...

An important test case is missing. See codecov diff: https://codecov.io/gh/Eshaan7/flask-shell2http/src/master/flask_shell2http/classes.py#L146