Better way to consume global data build on shortcodes

[jeremenichelli]

Is your feature request related to a problem? Please describe.

Currently, if I declare global data in my config, for example...

export default function eleventy(config) {
  config.addGlobalData('buildTimestamp', () => {
    return new Date().toISOString();
  });
}

When I wanted to consume this single point of data inside a shortcode I had to do a really deep debugging around context of execution, and I reached to this:

function shortcode() {
  const buildTimestamp = this.ctx.environments.buildTimestamp;
}

It feels that I am in unsafe territory consuming something like this.

Describe the solution you'd like

I think the developer experience could be improved by two things:

1. Exposing a better namespace for this, my suggestion would be no acronyms, better naming: this.context.data.
2. Documenting this context object so there are clear expectations on how it will behave, plus it feels I am consuming this data in the way is intended and is safe for future upgrades of the package.

Update

I notice we have an eleventy object available in shortcodes, it would be good to populate that with context data like this.eleventy.data or this.eleventy.context.data.

Describe alternatives you've considered

No response

Additional context

You can see this working in my personal site repository:

• https://github.com/jeremenichelli/jeremias.codes/blob/main/eleventy/shortcodes.js#L12
• https://github.com/jeremenichelli/jeremias.codes/blob/main/.eleventy.js#L32