Skip to content
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

Docs: “Global data files” should address non-camelCased filenames, name collisions #1424

Open
Zearin opened this issue Jun 12, 2022 · 1 comment

Comments

@Zearin
Copy link
Contributor

Zearin commented Jun 12, 2022

The example on the Global data files uses a hypothetical file called _data/userList.json.

But what if...

  • …the user has a data file named user-list.json instead?
  • …there exists both a folder _data/users/ and the file _data/users.js?

    (This is a pretty common pattern, where top-level file’s name matches a folder name containing details )

Eleventy’s behavior in these cases should be documented.

@Zearin
Copy link
Contributor Author

Zearin commented Aug 28, 2022

ping

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant