-
Notifications
You must be signed in to change notification settings - Fork 29
messaging: move docs to Markdown and never throw on calls to .notify #1817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
messaging: move docs to Markdown and never throw on calls to .notify #1817
Conversation
✅ Deploy Preview for content-scope-scripts ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Temporary Branch UpdateThe temporary branch has been updated with the latest changes. Below are the details:
Please use the above install command to update to the latest version. |
[Beta] Generated file diffTime updated: Fri, 11 Jul 2025 18:25:38 GMT Android
File has changed Chrome-mv3
File has changed Firefox
File has changed Integration
File has changed Windows
File has changed Apple
File has changed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR extracts inline documentation into standalone Markdown files for better maintainability, updates the Typedoc configuration to include the new docs, and ensures .notify()
calls never throw by wrapping them in a try/catch (with a corresponding unit test).
- Move native.js inline docs into
messaging/docs/
Markdown files (messaging.md
,implementation-guide.md
,examples.md
) - Update
typedoc.js
to include the top‐levelmessaging/docs/messaging.md
- Wrap
transport.notify
in a silent try/catch and add a unit test to verify no exception is thrown
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
File | Description |
---|---|
typedoc.js | Includes messaging/docs/messaging.md in the Typedoc config |
messaging/native.js | Remove large inline doc comment, replace with module link |
messaging/index.js | Wrap transport.notify in try/catch and update JSDoc comments |
messaging/docs/messaging.md | New high-level Markdown overview for Messaging API |
messaging/docs/implementation-guide.md | New platform implementation guide Markdown |
messaging/docs/examples.md | New example payloads Markdown file |
injected/unit-test/messaging.js | Add unit test ensuring .notify() doesn’t throw on errors |
Comments suppressed due to low confidence (1)
typedoc.js:10
- The Typedoc include pattern currently only adds
messaging/docs/messaging.md
, but theimplementation-guide.md
andexamples.md
files won't be processed. Consider changing it to a glob likemessaging/docs/*.md
or adding individual entries for those Markdown files so all docs are published.
'messaging/docs/messaging.md',
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to validate all consumers of notify don't expect the throw? I know for bridge you were using it as a proxy for lack of support right?
@cursor anything to add? |
Leave me unread then. 😢 |
No, the bridge only delegates to the transports regardless. |
…ver_throw_on_calls_to_.notify
…1817) * messaging: move docs to Markdown and never throw on calls to .notify * add development debugging so that generic implementation errors are not lost
Asana Task/Github Issue: https://app.asana.com/1/137249556945/project/1201141132935289/task/1210768128803703?focus=true
Description
Small improvements towards https://app.asana.com/1/137249556945/project/1201141132935289/task/1210680503659356?focus=true
Testing Steps
Checklist
Please tick all that apply: