Support custom extensions for data providers

[cfjedimaster]

Is your feature request related to a problem? Please describe.
Note, I don't think this is the same as #117, but I could be wrong.

I do a lot of work with GeoJSON files (https://geojson.org/). They are JSON files but (typically) use the .geojson file extension. Putting one of these in _data will not work because 11ty will not recognize it as JSON.

Describe the solution you'd like
I'd like a configuration setting that would let me specify a file extension pattern, or list, to be treated as JSON.

Describe alternatives you've considered
Renaming the file. :) That works.

[Ryuno-Ki]

Hm, could you workaround with collection (glob flavour) or data files until #117 is implemented?

[cfjedimaster]

How would collections help? And to be clear, I meant data files. If it wasn't clear in the issue above let me know and I'll rewrite.

Basically, let me say that _data/cats.geojson is a valid data file by telling 11ty to look for *.json and *.geojson. The default would be *.json.

[saenglert]

Had a similar problem. I wanted to create a collection out of json files in my data folder. Eleventy treated them as individual data files. So I created a directory data file in the JS format which means I can use Node to manually load, parse and return the files as JSON objects:

const fs = require("fs");
const path = require("path");

const jsons = fs.readdirSync(__dirname, {withFileTypes: true}) // Get all files in dir
.map(file => file.name) // Map all files names
.filter(name => /(.+)\.json$/.exec(name)) // Filter all .json files
.map(name => fs.readFileSync(path.resolve(__dirname, name))) // Read .json files
.map(buffer => JSON.parse(buffer.toString())) // Parse to json object

module.exports =  jsons;

Might be overkill but worked for me :)

Edit: Of course depending on the size of your files you might want to switch from sync to async file operations

[Ryuno-Ki]

I had a similar approach like @saenglert in mind.

[Ryuno-Ki]

Glob collection would be https://www.11ty.io/docs/collections/#getfilteredbyglob(-glob-)

[cfjedimaster]

Glob collection would be https://www.11ty.io/docs/collections/#getfilteredbyglob(-glob-)

I don't get that how that would help for a data file though? Basically I want foo.geojson to be available as foo in my templates. It's not a collection, just data. I'd like Eleventy to basically let me configure: "In _data, what files do I consider JSON files."

Does that make sense?

[saenglert]

Yes it does, @cfjedimaster.
However, as @Ryuno-Ki already pointed out this is not possible as #117 is not implemented yet. So you need a workaround.

Now my approach returns the data as unsorted array. You want to access your files by filename. This means some modifications are required.

[cfjedimaster]

Ok, so when I wrote this bug, I thought maybe 117 wasn't going to cover it. If you think it will, I'll gladly close this as a dupe. :) Thanks!

[gloryofrobots]

You probably can do it with new custom data files feature that just get merged #798
eleventyConfig.addDataExtension("geojson", contents => JSON.parse(contents));

[zachleat]

#635 #798 aren’t quite aliasing but since it’s JSON I think that lovely addition by @gloryofrobots will solve this particular issue nicely.

Just for pedantic reasons I’ve filed #801 if people want fancier data file aliasing moving forward. #207 is the issue for template file aliasing.

[zachleat]

Closing as a duplicate of #630. Look for this feature in 0.10.0!