woohaaha
Absinthe GraphQL viewer/me pattern
There is a pattern in GraphQL called viewer. Using the example in the Absinthe book the me is the root viewer:
{
me {
orders {
id
items {
name
quantity
}
}
}
menuItems {
name
}
}
It is still not so clear to me how to implement this. I did some searching online as well and couldn’t find any examples.
Does anyone have any examples of how to implement the root viewer pattern with absinthe?
Thank you
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked
benwilson512
I can’t say I have much insight into the ex-Facebook crowd. I think whether or not
meis a useful pattern depends a bit on how you do authentication and authorization in your application. If you have entities owned by the current user then I definitely think it makes sense to scope it under that. It gets a bit trickier if you’re using role based authentication and authorization is less about “me” and more about “the role I want to use for this request”.You can also find minor inconsistencies between the
mepattern and thenodepattern. I absolutely adore thenodefield pattern because it saves you from redundantly setting up hundreds of “get this entity” fields. However it’s{ node(id: $id) { ... Fields } }not{ me { node() } }, but of course the permissions you have will affect whether or not you can access it.Really though I think the decline of
meorvieweris less about it not being a good idea, and more about the ex-Facebook crowd wanting to distance themselves from a dogma which made it a required pattern. Early versions of Relay (Facebook’s client) were exceptionally dogmatic with respect to how the schema needed to be organized, and it has tried to become more flexible over time.I suppose where that is leaving me is this: I think
meis a valuable pattern for accessing user specific data. I do not necessarily think that it is the most consistent pattern for acting as the primary entrypoint to the rest of the graph. However if that’s the route you want to go I think there can still be real upsides, so it’s a judgement call you’ll have to make.hykw
Does this showcase help you?
https://github.com/hykw/absinthe_showcase/blob/master/docs/operations/query_profile.md