Mo

The main issue seems to be that data is null. Is graphql not executed as the current user?

robbieaverill

i think you should expect graphql requests to be stateless. the module will authenticate using your logged in session, but if you were using something like basic auth instead it uses your verified Member as context but doesn't actually log that member in. session data shouldn't persist between the app layer and graphql responses, or between graphql requests

Mo

BUT if I do a var_dump during a graphql request, I get this:

Mo

If I do a var_dump of the current Session when logged into the admin, I get the following:

Mo

Does GraphQL somehow access different session data than a conventional SS request?

gened

Has anyone used this with SS for a front-end admin? https://github.com/marmelab/react-admin

Show 1 attachment(s)
marmelab/react-admin

A frontend Framework for building admin applications running in the browser on top of REST/GraphQL APIs, using ES6, React and Material Design

Hide attachment content
robbieaverill

React form fields are usually designed for the cms only. It might work, but you’d need to BYO React app and probably use injector (decoupled POC for frontend available on request) in order to make it work