Docs: backward-incompatibility notice
See original GitHub issueIt would be useful to put a notice in the docs regarding the change of methods->properties in your user class.
Probably 99% of apps out there uses the current_user.is_authenticated()
call in templates or code.
I needed some time yesterday to figure out why that code started to fail on a production environment. 😄
I can do a pull-request for this if you like.
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Recent changes to subscriptions in Play Console
Marking a base plan or offer as backwards compatible. When older subscriptions were converted into the new model, if the subscription contained a...
Read more >Backwards compatibility across updates - GitLab Docs
GitLab deployments can be broken down into many components. Updating GitLab is not atomic. Therefore, many components must be backwards-compatible.
Read more >Backwards Compatibility - SecurityScorecard API
All resources and representations are maintained in a backwards compatible manner (please see the section below for what are considered backward compatible ......
Read more >Backward Compatibility Policy | Commerce Contributor
This page describes rules and best practices for backward compatible development. See the versioning documentation for the definitions of ...
Read more >Google Docs and Backwards Compatibility
"Beginning today and rolling out over the next couple of weeks, all new documents will be created using the new documents editor. Docs...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Atorich version pinning is the correct solution.
Why this issue closed due to issue in another repo with non-constructive solution (to use flask-login==0.2.11) ?