Skip to content
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

Remote responses #36

Open
petterik opened this issue Jun 7, 2018 · 1 comment
Open

Remote responses #36

petterik opened this issue Jun 7, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@petterik
Copy link
Owner

petterik commented Jun 7, 2018

One of the things lost going from REST to om.next is remote mutation responses. Maybe even reads?

Where do we put them? We want to be app-state agnostic.

Into a layer? That's sweet?

Layers are also an answer to "is my request pending or not?".

@petterik petterik added the enhancement New feature or request label Jun 7, 2018
@petterik
Copy link
Owner Author

petterik commented Jun 9, 2018

In sulolive we (mostly) set states on a component whenever there was a new message, then we cleared it. We also checked if the message was pending in render.

Having a :lajter/responses {symbol (fn [this response])} might be enough for the state updating stuff?
Needs apis for:

  • checking status of a response
  • looking up the most-recent response
  • looking up all responses by key
  • looking up status on reads
  • test if the response was error or success

..more?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant