Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Deprecate and then rename/remove Page.URL #4117
I am not in favor of removing Page.URL.
But if you really think these are not valid use cases. Go ahead and remove it. I'll look into what can be done to replace its functionality... like I always do...
I agree there's some redundancy. And on one hand I think Hugo template code might become easier when there's no two variables that return the same data. But on the other hand the required conversion to string of
That latter might also make explaining how people can update from
Even though I wrote this without using programming lingo (like 'casting' or 'type incompatibility'), I still doubt if this is clear enough. (Or should we assume people read the release notes, where this can be explained more fully?)
So to summarise: I don't know what wisdom is for this issue.
If the recent release of Hugo 0.32 is any indication I would say that people don't bother with the release notes. The forum is full of posts regarding
A Warn like @Jos512 proposes is the way to go.
And possibly an example of the
You cannot assume that every user of Hugo has used every one of its functions or that he/she knows what to do in advance. Not all of us are from a Dev background.
I just want to say that the above approach would not work with
For example let's say that I have a section called
But thanks to Hugo 0.45.1 and
And then for other list pages within that Section I do the following simple check:
So at this point, I am fine with
And that is not a bad thing.
Since it will force theme authors to update their themes or if they don't we can always clean up the showcase from unmaintained themes.
So +1 for this issue.