You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 30, 2018. It is now read-only.
Create a new version of dojo/diagnostics that can be integrated into dojo/widget-core to produce messages that can be consumed by a browser plug-in.
Here are some requirements that must be fulfilled:
Calls to the diagnostics API from Dojo libraries must follow a syntax that can be identified and removed by the Dojo 2 builder (Webpack). A suggestion... Use the dojo/has library to wrap the diagnostics calls. The Dojo 2 builder already has the capability to remove code based on feature detection.
if(has('diagnostics')){diaganostics.log(...)}
Use postMessage to publish messages but also allow for messages to be transmitted via a web socket in the future for remote debugging.
For the initial implementation, publish a message that notifies when the virtual DOM is created/updated. Include the virtual DOM tree in the message.
Create a pull request that contains the modification to widget-core so it can be reviewed by the rest of the Dojo 2 team.
The text was updated successfully, but these errors were encountered:
Create a new version of dojo/diagnostics that can be integrated into dojo/widget-core to produce messages that can be consumed by a browser plug-in.
Here are some requirements that must be fulfilled:
postMessage
to publish messages but also allow for messages to be transmitted via a web socket in the future for remote debugging.For the initial implementation, publish a message that notifies when the virtual DOM is created/updated. Include the virtual DOM tree in the message.
Create a pull request that contains the modification to widget-core so it can be reviewed by the rest of the Dojo 2 team.
The text was updated successfully, but these errors were encountered: