Lily Acadia Gilbert
Lily Acadia Gilbert
This is happening because in most cases, `OPTIONS` is used as a preflight CORS check that happens automatically by the web browser, and when that happens the browser wont be...
Sorry for the late reply! > I would have expected get_jwt_identity() to return None as optional=True is passed and no JWT is present. Wouldn't that be the correct behavior It...
The reason we went with decorators instead of a more OOP approach was because that is the way most familiar for developers to interact with core flask and a bunch...
If I recall correctly, I tried something like that a long time ago, but ran into some issues I *think* around how to handle CSRF as required when dealing with...
flask-jwt-extended v3 required Flask < 2 because it was released 18 months ago, which was a few months before flask flask v2 was released. I don't remember what all incompatibility...
Sure thing. It should not be hard to break those into a help function and export them like what was done with the extended version of the library. If you...
@Colin-b Thanks for pinging me, I missed this ticket when it was first opened. My current plan is to depreciate this extension when I finish up the flask-jwt-extended 4.0.0 release....
Glad I wasn't the only one who made that mistake :)
This was the original reason why it is setup the way it is: https://github.com/vimalloc/flask-jwt-extended/issues/467#issue-1143611571 I'm honestly not sure what best practices would dictate here. I'll think on this, and welcome...
Perhaps check out https://github.com/vimalloc/flask-jwt-extended. It provides more leeway in this regard, as you define your own endpoint for authing, and once your code has run, you can use functions like...