-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Master list of Flask features we're missing #3
Comments
@chriddyp I'm not super familiar with Flask, so if you think there is anything that is absolutely essential that may not be obvious from studying the dash ecosystem, please let me know! |
I've tried to keep the list of flask specific things as small as possible.
AFAIK, users are only accessing the underlying web server (
|
Great, seems like most of things are already doable given @thomasp85's fiery/routr/reqres framework. |
Yeah - there're no deal breakers here - I'm planning to add standard authentication tools to
I have no experience with heroku so here we'll have to experiment - I cannot see why there should be any problems though (famous last words) |
Similar to dash, dasher takes a fiery (flask) server as input to the initialization method, and also exposes (modified version of) that server as a field, for example:
This allows folks to add/customize functionality of the underlying web server, which is great, but is bound to lead to scenarios where something is possible/easy in flask, but isn't (yet) easy-to-do via fiery. This comment/issue serves as a 'master list' of those (currently known) features (which I'm hoping will help us organize/delegate/motivate @thomasp85 into implementing more fiery methods/plug-ins):
(UPDATE: this won't be necessary Find an equivalent to SeaSurf()._generate_token() in R for CSRF protection #2)
The text was updated successfully, but these errors were encountered: