Ward Peeters
Ward Peeters
Closing bedcause of umbrella issue #2700
Not yet, but a good feature request to make our handlers more customizable
I'm working on something like this right now, which adds extra routes to hono server ``` new Mastra({ server: { port: 3000, middleware: () => { }, routes: [ registerApiRoute("/cool/stuff",...
Registering these routes is mainly to facilitate the injection of loggers and telemetry and to optimize these handlers in the future. What you might be looking at is https://github.com/mastra-ai/mastra/pull/3294, where...
Closing bedcause of umbrella issue #2700
I've started https://github.com/mastra-ai/mastra/pull/2950 to remove the default Pino logger from the equation so you can bring your own logger. I'll investigate if we can improve Pino as well. It's the...
We have removed the default logger pino in @mastra/core, so you can implement your own logger if you want to or use our default console logger
@Mrinank-Bhowmick if you put up a pull request we can do a code review and give pointers if necessary
Why do you need to set the resourceId through runtimeContext? Why can't you set it from the caller side? Because the user data might nog be secure from the caller...
@martijnthe What do you think of the following middleware ``` export const mastra = new Mastra({ server: { middleware: [ async (c, next) => { const runtimeContext = c.get("runtimeContext"); c.setResourceId(runtomeContext.get('my-custom');...