[ ] event processors - it's a pain to add to Windows Powershell due to the conflict with the Process keyword. Internally, we have a c# class that changes the call to DoProcess but modules don't really work well with exporting classes. Alternatively, we could have a Add-SentryEventProcessor which would take a scriptblock argument and we would wrap that in our internal EventProcessor implementation.
[ ] Dogfooding: use the SDK on our PS automation. Projects in sentry-sdks are prob good enough since the automations exist to support the SDKs
Processkeyword. Internally, we have a c# class that changes the call toDoProcessbut modules don't really work well with exporting classes. Alternatively, we could have aAdd-SentryEventProcessorwhich would take ascriptblockargument and we would wrap that in our internalEventProcessorimplementation.sentry-sdksare prob good enough since the automations exist to support the SDKs