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
Is your feature request related to a problem? Please describe.
I'm porting a personal project that makes heavy use of a data directory. In my old setup, I had already arranged my data into a hierarchical set of folders and files. I already had the data hierarchy exactly as I wanted it by simply importing (or require-ing) the top-level index.js file.
Although I think Eleventy’s built-in feature to construct the data hierarchy based on nested folders is a cool feature, I want to turn it off for this particular project. The data is now bloated with lots and lots of duplicates, and the hierarchy I had previously constructed now requires me to insert a lot of .index. everywhere («something».index.«something»), because I used the standard practice of using index files as the default place for importing data in each subdirectory.
Describe the solution you'd like
I want a boolean option in Eleventy’s configuration that allows me to turn off Eleventy’s automatic data-hierarchy feature.
The text was updated successfully, but these errors were encountered:
This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open.
Is your feature request related to a problem? Please describe.
I'm porting a personal project that makes heavy use of a data directory. In my old setup, I had already arranged my data into a hierarchical set of folders and files. I already had the data hierarchy exactly as I wanted it by simply importing (or
require
-ing) the top-levelindex.js
file.Although I think Eleventy’s built-in feature to construct the data hierarchy based on nested folders is a cool feature, I want to turn it off for this particular project. The data is now bloated with lots and lots of duplicates, and the hierarchy I had previously constructed now requires me to insert a lot of
.index.
everywhere («something».index.«something»
), because I used the standard practice of using index files as the default place for importing data in each subdirectory.Describe the solution you'd like
I want a boolean option in Eleventy’s configuration that allows me to turn off Eleventy’s automatic data-hierarchy feature.
The text was updated successfully, but these errors were encountered: