-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Update graphql, events & extending docs for Laravel and v4 #2026
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
Update graphql, events & extending docs for Laravel and v4 #2026
Conversation
Updated the documentation to reflect the requirement of `use_symfony_listeners: true` for activating event listeners in API Platform 4.0. Also reformatted existing notes for better clarity and added separation lines for improved readability.
This commit introduces detailed documentation on the workflow of state providers and processors in the system. It includes a schema, examples of decorating providers and processors, and specific implementations for both Symfony and Laravel frameworks.
This update adds detailed instructions for enabling and configuring GraphQL in a Laravel environment, complementing the existing Symfony guidance. It covers installation, route configurations, disabling features, custom resolvers, and altering default settings specific to Laravel, ensuring comprehensive and platform-specific documentation.
4a2a8cb
to
002cd75
Compare
Updated terminology from "stages" to "providers and processors" for better clarity. Removed redundant sections to streamline information on custom mutations and configuration examples.
002cd75
to
8495af2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great!
Co-authored-by: Kévin Dunglas <[email protected]>
Co-authored-by: Kévin Dunglas <[email protected]>
Co-authored-by: Kévin Dunglas <[email protected]>
Co-authored-by: Kévin Dunglas <[email protected]>
Co-authored-by: Kévin Dunglas <[email protected]>
Co-authored-by: Kévin Dunglas <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, on graphql we also need to document how to secure routes using a middleware and probably also document policies.
Thanks, please let me know more about what's missing before we can merge. |
Co-authored-by: Antoine Bluchet <[email protected]>
Co-authored-by: Antoine Bluchet <[email protected]>
Co-authored-by: Antoine Bluchet <[email protected]>
Co-authored-by: Antoine Bluchet <[email protected]>
Co-authored-by: Antoine Bluchet <[email protected]>
Co-authored-by: Antoine Bluchet <[email protected]>
Co-authored-by: Antoine Bluchet <[email protected]>
Co-authored-by: Antoine Bluchet <[email protected]>
Co-authored-by: Antoine Bluchet <[email protected]>
Co-authored-by: Alan Poulain <[email protected]>
Co-authored-by: Alan Poulain <[email protected]>
Co-authored-by: Alan Poulain <[email protected]>
Co-authored-by: Alan Poulain <[email protected]>
Co-authored-by: Alan Poulain <[email protected]>
Co-authored-by: Alan Poulain <[email protected]>
@soyuka @alanpoulain Reviewed changes resolved! |
Co-authored-by: Alan Poulain <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't forget to squash!
Nice thanks! |
The initial aim was to update the
core/graphql.md
, but I soon realized, with @soyuka's help, that some parts didn't work like that anymore in API Platform 4 (for example the "stages").So we decided to move and rewrite some parts in
core/extending.md
and add a warning incore/events.md
documentations.