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
Bumping minimum version is not a light decision, especially of such a big leap.
But as we want to keep the theme supporting older versions, we need to be able to secure new features behind version conditionals.
While we can test hugo version with {{ if ge hugo.Version "0.70.0" }} since 0.63.0, testing if user is using Hugo extended which allows sass and webp image processing is only possible since 0.83.0 with hugo.IsExtended. (see #452)
Also 0.84.0 allows to id error messages which is very useful for themes.
I feel with a min version of 84 we'll be more confortable using Hugo's latest features while maintaining cross compatibility of the theme users.
The text was updated successfully, but these errors were encountered:
Bumping minimum version is not a light decision, especially of such a big leap.
But as we want to keep the theme supporting older versions, we need to be able to secure new features behind version conditionals.
While we can test hugo version with
{{ if ge hugo.Version "0.70.0" }}
since0.63.0
, testing if user is using Hugo extended which allows sass and webp image processing is only possible since 0.83.0 withhugo.IsExtended
. (see #452)Also 0.84.0 allows to id error messages which is very useful for themes.
I feel with a min version of 84 we'll be more confortable using Hugo's latest features while maintaining cross compatibility of the theme users.
The text was updated successfully, but these errors were encountered: