Don't create page bundle as a result of a dangling resource

[bep]

Given a fictional site with languages en, jp and sv there are currently 2 conventions re. bundles and their resources vs languages.

Given this example:

content
└── mybundle
    ├── data.en.json
    ├── data.jp.json
    ├── data.sv.json
    ├── index.en.md
    ├── index.jp.md
    └── thumb.jpg

Hugo will:

1. Return the same logical set of resources (thumb.jpg and data.json) when calling $mybundle.Resources regardless of language.
2. Will create the missing sv version of mybundle to make data.sv.json navigable.

I'm in the process of simplifying/improving the above to enable some cool stuff, and with that I had a test failing for the 2) case above which I, even after thinking about it for a day, find surprising. I do agree that we need some better setup for filling in missing translations (e.g. lang={en,sv,jp}), but the behaviour in 2) isn't a great way to do this. Also, and this is the most important to me at the moment, it makes what I'm about to do really clumsy and hard to implement.

Note that this is only about the 2) bullet above.

[bep]

This if fixed.

[github-actions]

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.