-
Notifications
You must be signed in to change notification settings - Fork 6
Incorporate poke-proxy-hook #19
Comments
Adding link to current designs: https://www.figma.com/file/i7ssONyMpqgW4f6FeKEmtj/OS2?node-id=7698%3A634 We're speaking specifically to the 'bookending' interfaces on the viewport's header and footer, indicating that the state of the channel is in a "loading" state. A separate but related component to make note of is our current "Reconnecting" label that pops up in the header: It's likely we should generalize this component/label such that we can display general "thinking" or "spinner" components here. |
We can have a double pending state (sent vs. delivered). |
If we write "lib/poke-proxy-hook" — When we poke remote, we'll poke it through some hook and it'll blindly pass on the poke to the remote; but we don't have any machinery in place to say "we submitted this and haven't heard from remote" or to surface that a remote declined. |
urbit/urbit#4106, some other proxy work and conversations in urbit/urbit#4268 |
Closing in favour of implementing remote pokes in eyre |
The text was updated successfully, but these errors were encountered: