setting pagination with eleventyComputed and then using pagination.item[0] in an eleventyComputed permalink

[olets]

I have a several paginating templates. Currently they all have similarpagination frontmatter, and shared permalink logic in a data file:

(note: no I don't really use these directory/file/data/alias names. they're for the demo)

.
└──  paginateds
     ├── paginateds.11tydata.js
     ├── dir1
     |   └──  template.njk
     └── dir2
         └──  template.njk

---
# paginateds/dir1/template.njk
pagination:
  alias: myalias
  data: data1 # every item has a `permalink`
  size: 1
---

---
# paginateds/dir2/template.njk
pagination:
  alias: myalias
  data: data2 # every item has a `permalink`
  size: 1
---

// paginateds.11tydata.js
export default {
  eleventyComputed: {
    permalink: ({ pagination }) => pagination.items[0].permalink,
  }
}

To reduce boilerplate I'd like to move the overlapping parts of the pagination configurations to the data file too. Something like this:

---
# paginateds/dir1/template.njk
paginationData: data1 # every item has a `permalink`
---

---
# paginateds/dir2/template.njk
paginationData: data2 # every item has a `permalink`
---

// paginateds.11tydata.js
export default { // I'm using ESM with the latest v3 canary (3.0.0-alpha.14)
  eleventyComputed: {
    pagination: ({ paginationData }) => ({
      alias: "myalias",
      data: paginationData,
      size: 1,
    }),
    permalink: ({ pagination }) => pagination.items[0].permalink,
  }
}

 

expand for side quest: why a new frontmatter key paginationData?

This

---
pagination:
  data: # …
---

Triggers the error

Missing pagination size in front matter data

 

The pagination template config part of that works —the expected pages are generated, the size is right, the alias works— but ⚠️ it breaks the permalink. Apparently when pagination (the template config) is set with eleventyComputed, pagination (the pagination data — items, etc.) is not available at the time that eleventyComputed computes the permalink.

Is there a way around this?

One thought I had was to try using pagination.before to try to encourage the resolution of the pagination data (the items, etc).

// paginateds.11tydata.js
export default {
  eleventyComputed: {
    pagination: ({ paginationData }) => ({
      alias: "myalias",
      before: (paginationData) => paginationData,
      data: paginationData,
      size: 1,
    }),
    permalink: ({ pagination }) => pagination.items[0].permalink,
  }
}

but it doesn't help.

Maybe there's some async/await hackery solution. I expect the overlapping names pagination and pagination will complicate things.

[olets]

Got it

Non-eleventyComputed data file data must be read earlier because this works

---
pagination:
  data: # …
---

export default { // I'm using ESM with the latest v3 canary (3.0.0-alpha.14)
  eleventyComputed: {
    permalink: ({ pagination }) => pagination.items[0].permalink,
  },
  pagination: {
    alias: "myalias",
    size: 1,
  }),
}