-
-
Notifications
You must be signed in to change notification settings - Fork 294
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
TODO: support the incoming v2.0 release of flask-admin #753
Comments
[#753] temporarily block flake-admin-v2 & actualize install instructions
If we have enough users requiring a patch, we'll release one. Else it would be a regular release. |
We still haven't released a version with the fix for #729 (even though the fix was merged in April) |
Right, I am still waiting since only one user reported it... so it may not be a widespread issue right now. |
Rather than not being widespread, that user noticed it immediately due to running his own tests in a package manager repo, essentially 😅 (And I guess most Buku users who visit GitHub are already used to running nightly, seeing as they couldn't install the latest version from PyPI for months if not years by that point 🤔) |
Can you make a release? Please let me know if you need anything. Release checklist: https://github.com/jarun/buku/wiki/Release-checklist |
I'd rather wait for the release of the new |
Note: Flask-Admin made a v2.0.0a0 pre-release; though v2.0 changes are not finalized yet |
i18n
Currently (as of v1.6.1),
flask-admin
i18n depends onflask-babelex
if it's present, falling back toflask-babel
otherwise. Meaning,flask-babel
is only used whenflask-babelex
is not installed. For that reason, we're doing the same thing exactly.However, recently
flask-babel
repo got a breaking change merged in, removing all dependencies onflask-babelex
. They're planning to make a release candidate for the next version soon (appropriately numbered v2.0, since it includes breaking changes).We should include appropriate changes in the next (patch?) release, migrating to the new
flask-admin
version once it's available, and removing dependency onflask-babelex
accordingly.bootstrap
The incoming release of
flask-admin
is going to drop the support for Bootsrap2 & Bootstrap3 themes. We're currently using the Bootstrap3 theme, so migrating bukuserver to Bootstrap4 would be necessary.(Note: Bootstrap4 is supported by the version of
flask-admin
we're currently using, so we don't need to wait for the next release offlask-admin
to implement this chance)The text was updated successfully, but these errors were encountered: