Eaton
I am *unhealthily* excited about a feature that snuck its way into the latest canary release of @eleventy — plugins and other code can now insert arbitrary “pages” into the rendering pipeline, with all the metadata that would normally come from a physical file on disk.
That will make it way, way easier for plugins that retrieve data from headless APIs to do things like “check for collisionswith an existing file-based page before injecting a dynamically generated one”.
Eaton
@db @eleventy same! I spent a silly abount of time trying to get paginated collections to “skip” entries if an explicit file already existed on disk for a given item, but it really didn’t work given the way 11ty prebuilds template/file data. This seems to eliminate that problem entirely, making it easy to have a “standard” template for some api driven content, and a custom one for “special” pages. Super exciting.
Dan Burzo
@eaton @eleventy That’s cool, can’t wait for it to hit stable!
Eaton
@db @eleventy by default they throw on conflict, same as if you have two templates with colliding permalinks. But this approach gives a controlled place to do testing logic (ie, “does something already exist in the pile of pages to be rendered? Is there a file on disk that “claims” a given content id in its frontmatter?”) before programatically injecting a virtual file for the content. With the pagination method, I could never find a reliable way to do that.
Dan Burzo
@eaton @eleventy Found the discussion / commits, but I’m confused on how virtual/physical conflicts are handled. Does the virtual front-matter data override the physical front-matter data? Does Eleventy throw? Should I be able to check for the conflict beforehand, or do I do fs.exists()?
https://github.com/11ty/eleventy/issues/1612#issuecomment-2026201910
Eaton
@db @eleventy TBF this might be an extremely niche scenario, I’m just stoked at the flexibility the patch enables. Good times!
Eaton
@eleventy @db “first one wins, last one wins, die on error” with the latter as a default would be *super dope*
Eleventy 🎈 v3.0.0-alpha.20
@db @eaton we could pretty easily add an advanced option to skip on file system collision, if that would be helpful! Worth filing?
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.