-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Conversation
4943bc3
to
0768cf8
Compare
4ca015b
to
5298015
Compare
@yungsters @steveluscher @spicyj Thoughts on moving forward with this? |
}); | ||
}); | ||
bridge.on('relay:success', ({id, response, end}) => { | ||
console.log('response', id, response); |
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.
We should remove these.
Conflicts: agent/Bridge.js frontend/Panel.js frontend/SplitPane.js frontend/decorate.js
A better approach migtht be to implement a handshake on either the `Bridge` or `Wall` level that confirms that both sides are ready before sending anything.
Only show the Relay plugin for now as long as `location.hash` contains `relaydevtools`.
@yungsters and I thought it's best to land this (behind the URL toggle) and then iterate. |
At one point I had a settings tab see branch here, where I planned to allow users to enable/disable various plugins. That way you wouldn't need the location.hash thing. |
@jaredly: Yeah, I saw that but it didn't seem worth it for a single option. Once, we evolve the plugin a bit more, I think we can enable most things just when we see it's being used on the page. |
Other things that a settings page would be useful for: I agree that relay should only appear when it's detected though |
This is mostly @jaredly's work to add an initial plugin for Relay.
It currently includes #186, but I'll rebase once that's landed to clean this PR up.
I've fixed lint and flow issues as well as actually disabled this plugin by default. Since we don't have options yet, it's just commented out in
Panel.js
.It's the beginning of #187.