You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our API is never up to date with babel (ex: #142), and we do not cover the entire babel API. Our wrappers add no real value, and add a lot of surface area for test coverage. Just like flask-wtforms did way back in version 0.9, we should focus on just being the glue between flask and babel.
format_datetime
format_date
format_time
format_timedelta
format_number
format_decimal
format_currency
format_percent
format_scientific
As part of this, we need to improve the documentation to show better examples of using get_locale and get_timezone.
The text was updated successfully, but these errors were encountered:
while I do agree with this move, I'd like to point out that while Flask-Babel's format_date rebases according to the time zone, Babel's format_datedoes not. This might be a bad surprise for users after upgrading to v3.0.
I have raised an issue against Babel, hoping that Babel will gain this ability. But I guess it could use some more backing.
Our API is never up to date with babel (ex: #142), and we do not cover the entire babel API. Our wrappers add no real value, and add a lot of surface area for test coverage. Just like flask-wtforms did way back in version 0.9, we should focus on just being the glue between flask and babel.
As part of this, we need to improve the documentation to show better examples of using
get_locale
andget_timezone
.The text was updated successfully, but these errors were encountered: