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

Re-vamp book and code to stress server-side use of Pathom #288

Open
awkay opened this Issue Jan 25, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@awkay
Copy link
Member

awkay commented Jan 25, 2019

The book needs to show how to structure a more complete app with full-stack use of Pathom. The server-side defmutation and defquery should be discouraged (dropped from docs, even).

I don't necessarily see a need to make it a specific dependency of Fulcro's...since I'm going to stress writing your own server over the old pre-written stuff.

Ideally this content would also include how to server EQL through lacinia for GraphQL clients.

@awkay awkay added the enhancement label Jan 25, 2019

@awkay awkay added this to the Fulcro 3.0 milestone Jan 25, 2019

@wilkerlucio

This comment has been minimized.

Copy link
Member

wilkerlucio commented Jan 28, 2019

I like the idea, just not sure about the Lacinia thing, instead of making it expose EQL (which I think would be a lot of work) we can teach people to use Pathom on the client connect to any GraphQL backend (that could be Lacinia or anything else), IMO will be a simpler path that already works.

@awkay

This comment has been minimized.

Copy link
Member Author

awkay commented Jan 28, 2019

The benefit of using EQL is that it is more powerful....I've alraedy written a layer for Lacinia that works well, and is easy to add on...that let's clients still use placeholders, etc. The GQL stuff is just in case you need external API AFAIC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment