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
I know there are many that uses .Path to construct links to the file on GitHub etc., and I suspect many implementations do not consider the case where the Page is not backed by a file.
In 0.92.0 you will get a deprecation WARNING if the Page is backed by a file with the advice of rewriting it to something ala:
This is preparing for a bigger 0.93.0 release which introduces a concept of a canonical content path.
The current implementation looks like this:
I know there are many that uses
.Path
to construct links to the file on GitHub etc., and I suspect many implementations do not consider the case where the Page is not backed by a file.In 0.92.0 you will get a deprecation
WARNING
if the Page is backed by a file with the advice of rewriting it to something ala:The text was updated successfully, but these errors were encountered: