new-subsubsection-slide-fn does not seem to work?

[joelvonrotz]

Hello everyone,
I'm trying to create my own template and wanted to keep the level-3 headings on a separate slide. In the template, I've added a new function called new-subsubsection-slide to the respective slide function callback:

show: touying-slides.with(
    config-common(
      slide-fn: slide,
      new-section-slide-fn: new-section-slide,
      new-subsubsection-slide-fn: new-subsubsection-slide,

    ),

And the function is defined as following:

#let new-subsubsection-slide(self: none, body, ..args) = touying-slide-wrapper(self => {
  set text(font: self.store.font.paragraph)
  let header(self) = {
    set text(font: self.store.font.headfoot, 24pt)
    set align(center)
    box(width: 100%)[
      #set align(left)
      #box(inset: (x: 4mm, top: 4mm))[
        #set text(12pt, self.colors.tertiary, style: "italic")
        #build_breadcrumbs(dot-color: self.colors.tertiary-light)
        #h(1fr)
        Slide #context{utils.slide-counter.display()}
      ]
    ]
    v(1fr)
  }

  self = utils.merge-dicts(
    self,
    config-page(
      header: header,
      margin: (top: 2cm, bottom: 2cm, x: 1cm),
    ),
  )

  touying-slide(
    self: self,
    {
      set align(center + horizon)
      grid(rows: (1fr, 0pt, 1fr), row-gutter: 8mm)[
        #set align(bottom)
        #set text(size: 70pt, weight: "bold", font: self.store.font.heading)
        #utils.display-current-heading(level: 2)
      ][
        #line(
          length: self.page.width - 4cm,
          stroke: (dash: (5pt, 6pt), cap: "round", thickness: 2pt, paint: red),
        )
      ][
        #set align(top)
        #body
      ]
    },
  )
})

Even with this configuration, the level-3 headings do not get their own slides:

for

== Software

#lorem(30) #todo[Push & Pull Erwähnung]

=== AT Parser

=== Hello

- AT Parser
- 
- evtl. Skalierung

Is this a bug or did I forget to configure something?

[OrangeX4]

Whether you have set slide-level?

[joelvonrotz]

Whoops, didn't know this was a feature... This fixed it! Thank you!