-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Glob patterns in v0.123.0 #11977
Comments
The above should work (for backwards compability), I guess (I find it unusual to have a Gob path pattern without any asterisk in it -- why not put that value directly into the file you target?) Edit in: I will try to make the above cases work, but I will issue a warning about it. The meaning of |
The |
Edit in again: I think we need to apply a proper fix here, else we're going to have to maintain these special cases forever.
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I was sort of expecting this, but using a
path
Glob pattern while cascading a value seems to look for the canonical page path.I'm not sure this is a bug, but the behavior has changed from v0.122.0.
content/_index.de.md
The above works in v0.122.0.
But this is required in v0.123.0:
We use Glob patterns elsewhere, but I didn't check any of those.
I'm also not sure how the
lang
keyword is supposed to work in this situation. It seems like it should be ignored (it is) when cascading from a node.Finally, the example above may not be realistic. I think in most cases the Glob pattern is used to target a directory instead of a page, but I could be wrong.
The text was updated successfully, but these errors were encountered: