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
Expected hugo --printPathWarnings to detect collision.
By comparison, content tagged with "a,b" and "a;b" report a page collision (as expected), because they are both published to public/tags/ab/index.html.
The text was updated successfully, but these errors were encountered:
Expected hugo --printPathWarnings to detect collision.
On the technical side, --printPathWarnings keeps track of filenames written to /public and print a warning if more than file is written to the same path.
The case in this issue happens earlier, and it's not obvious to me (at least in the general case) when it is a warning or not. The thing is, we already do lots of content merging where you will e.g. have files in project mounts etc. with the same name as in the theme, and we don't call these collisions.
That said, we should improve this, but it's not obvious to me what/how.
This isn't anything new. Behavior present since v0.55.0.
Expected
hugo --printPathWarnings
to detect collision.By comparison, content tagged with "a,b" and "a;b" report a page collision (as expected), because they are both published to public/tags/ab/index.html.
The text was updated successfully, but these errors were encountered: