David Cramer
David Cramer
I'm not sure this makes a lot of sense. We'd be duplicating information that we'd have to maintain between multiple repos of docs. We can say "Configuration happens within your...
I'd rather this be supported via `sentry.options`. Environment variables are problematic for various reasons, and we're never going to support "configure everything with env vars".
Best bet is to look in sentrys code on GitHub. src/sentry/options. Specifically you need .register and .get. We also don't have a way to expose these via web UI yet...
Definitely. We could probably do it in the base issue plugin which is part of sentry core On Mar 14, 2013, at 3:06 PM, Zach Smith [email protected] wrote: > Would...
@icedfish repo is requested right now because sentry-github needs it. We could probably be smarter about this, but I feel like the only way we could _really_ do that is...
I'm not sure how this is really any different. Appears to me its just adding "for example", and makes the formatting less structured around it.
almost sounds like its treating
FYI still seeing this in latest ``` "@mastra/core": "^0.10.5", "@mastra/libsql": "^0.10.2", "@mastra/loggers": "^0.10.2", "@mastra/memory": "^0.10.3", ``` Got here via Google, but current open ticket is #4822
I realize this is dangling, but one thing I wanted to mention here: you should keep mcp.transport. Abstracting this purely to the network transport removes the value conventions add. For...
This reminds me of past convos now: is spotlight just better as a desktop app?