feat: add manual error capture

[ioannisj]

💡 Motivation and Context

Part of PostHog/posthog#38845
Needs PostHog/posthog#39738

Docs: PostHog/posthog.com#13356

💚 How did you test it?

📝 Checklist

• I reviewed the submitted code.
• I added tests to verify the changes.
• I updated the docs if needed.
• No breaking change or entry added to the changelog.

[ablaszkiewicz]

Never seen dart before but looks legit

I figured I should not be approving that

[ioannisj]

Phew 😅 ~100 comments later.. i think i’ve covered most of it now. sorry for the chaos in this pr

[marandaneto]

Phew 😅 ~100 comments later.. i think i’ve covered most of it now. sorry for the chaos in this pr

i hope they were valid and useful and not just nitty :)

[marandaneto]

@ioannisj asked on the official docs but worth checking, do we need a guardrail for flutter web?

[ioannisj]

Phew 😅 ~100 comments later.. i think i’ve covered most of it now. sorry for the chaos in this pr

i hope they were valid and useful and not just nitty :)

Of course they were, as always! Mille grazie!🙏

[ioannisj]

@ioannisj asked on the official docs but worth checking, do we need a guardrail for flutter web?

Replied there PostHog/posthog.com#13356 (comment). Pushed a commit and now captureException is a noop on web

Question is, should we add support now? I'd have to see how this will play with js config options. We have the event data and props, so we may as well capture the event. My take is focus on mobile for now, then come back to web? wdyt?

[ioannisj]

@ioannisj asked on the official docs but worth checking, do we need a guardrail for flutter web?

Okay took a while but validated that web runs okay so worth including. Had a rough time with js interop but managed to figure it out thanx to this

Tested for default as well WebAssembly build modes.

When building with --wasm, I saw that some function names were leaking some PII. They had the shape of module0.InitialScreenState.build closure at file:///path/to/file.dart:251:30. Tried extracting just function name part in those cases. It might not catch every shape, but we can iterate once we see real world reports (this could even be just because of running locally maybe).

--no-wasm

--wasm

console

[ioannisj]

Will release this one and we can revisit on this comment if needed