Why _SAVE_AS and _URL? #3545
Dreamsorcerer
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
|
One example: If you create a page and if you set (You would probably do this by setting the page metadata rather than using the settings in your |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm confused by the presence of both _SAVE_AS and _URL variables.
It seems to me that whatever you set a _SAVE_AS variable to, the _URL must then be set to exactly the same thing or (and only if it ended with index.html), the same thing with index.html stripped.
This seems like it's easy to misconfigure and mess up (e.g. #1188), while not providing any benefits I can see...
If there are at most 2 valid values for _URL variables, why not just have a bool, such as PREFER_SLASH_URLS or STRIP_INDEX_FROM_URLS? This could then be applied generally across the project without needing to configure a dozen different variables.
e.g. Everytime a URL is output, the code could just do:
I'm wondering if there's some other use case I'm missing here?
Beta Was this translation helpful? Give feedback.
All reactions