[RFC] Improving/rethinking the trigger events processing about hono-adapter-aws-lambda HOT 1 OPEN

I have just released a canary version for the PoC of the new processing of trigger routes, here is some notable features:

• Multiple routes is now possible to be registered for the same eventSource, as in the first post.
  • You can use $! (rootTakeover) and $= (rootReturn) as the route id for some edge cases such as returning a stream.
• Factory pattern, less of weird getTriggerPath() and manual .on('TRIGGER') method declare, now just create a factory from the root instance, import it anywhere and triggerFactory.on(eventSource, routeId, ..handlers), fully middleware handlers support just like normal Hono route!
  • It's possible to also allow factory to be created from sub-instances and still works but I don't think it's a good pratice, so for now only the routes declared from the factory created from the root instance will be effective.
• The internal triggers context uses it's own Hono instance, to decouple from your main Hono router, this is because most likely you will have many middlewares and env bindings registered that is not compatible/intended for the trigger event.
  • You could register middlewares for the trigger routes by accessing .internalApp on the factory.

from hono-adapter-aws-lambda.