Wow, I almost forgot about this book, what a throwback

"exposition comics", maybe? Then you can shorten it to "expo comics" (not to be confused with comics found at expos/conventions).

Awesome! I had a feeling it should work, just haven't seen anyone use that way before, at least not in most tutorials ive encountered. Good to know that you have alternative options for the callbacks.

Yes! Thank you for linking the docs for this feature. I only stumbled upon it earlier this year through a random Stackflow post lol

I ended up using this syntax for my own router library where middleware are passed this way as callable spread arguments.

Oh, no it wouldn't cause the app router isn't expecting the direct reference, it's expecting an array with the class and a string name. My original question was to ask why the 3 dot syntax isn't supported

Totally fair lol I actually only found out about that syntax earlier this year, and I love it more than just a string name, cause it enables actual reference highlighting in the editor, and I can easily jump to its definition.

Ah, okay that's a good reason for the ::class syntax: to instantiate a controller and do some setup. The specific 3 dots syntax inside the parentheses is what I'm talking about, which actually doesn't execute the function, it passes it as a closure-like callback; I'll find the docs later

It actually is passing it and not calling. I can't find the docs on mobile, but the 3 dots in between the parens is actual syntax 8.x that passes the function reference instead of calling it.

But why the array with 'MyClass::class' then 'static_class_method_name'? Why not just pass the static class method reference directly via 'MyClass::static_class_method_name(...)'?

This is the list I’m using, and then any others that slip through I’m just nuking on my own:

bsky.app/profile/did:...