| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Every delivery path built its MessageEvent through the public constructor, whose init dictionary turns an undefined data into null. Delivery now goes through an internal factory that stores the payload as given. The native messageerror paths pass null so that event keeps its default data, and a worker's messageerror carries the deserialization failure as its data, as a port's already does.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info ⚙️ Run configuration
Reviewing files that changed from the base of the PR and between 42a8bcf and 4f06805. 📒 Files selected for processing (10)
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 Walkthrough WalkthroughMessage delivery now uses a factory to preserve delivered undefined values in message events. Native deserialization failures use null when no exception value is available. Regression tests cover messaging channels, workers, and MessageEvent defaults. ChangesMessage data handling
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to 4f068 The change makes a posted undefined arrive as undefined instead of null across message ports, broadcast channels and workers. Regression tests cover these paths. No merge-blocking risk was found. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. ❤️ ShareA rabbit sends a message through the night, Comment @coderabbitai help to get the list of available commands. |
Sorry, something went wrong.
|
✅ Action performed
Review finished.
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
postMessage(undefined) arrives as null everywhere a message is delivered: a MessagePort, a BroadcastChannel, a Worker and its global scope, and a node:worker_threads parentPort. Node and browsers deliver undefined.
Every delivery path builds its event with new MessageEvent(type, { data, ports }), and the constructor's init dictionary turns an undefined data into null, as Web IDL requires. Delivery now goes through an internal createMessageEvent that stores the payload as given, the same fix as NativeScript/ios#477. The native messageerror paths pass null instead of undefined, so that event keeps its default. A worker's messageerror now carries the deserialization failure as its data, as a port's already does and as NativeScript/ios#489 does on iOS.
Stacked on #2043. The new specs in testMessaging.js fail on that branch and pass with this change, and the full device suite passes.
Summary by CodeRabbit