Update graphql, events & extending docs for Laravel and v4 #2026
+499
−248
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
vinceAmstoutz
force-pushed
the
docs-update-graphql-support-doc
branch
from
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.
vinceAmstoutz
force-pushed
the
docs-update-graphql-support-doc
branch
from
002cd75
to
8495af2
Compare
vinceAmstoutz
changed the title
vinceAmstoutz
changed the title
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]>
soyuka
reviewed
Oct 3, 2024
|
|
||
| ### Symfony Access Checker Provider | ||
|
|
||
| When using Symfony, the access checker provider is used at three different stages: |
There was a problem hiding this comment.
For this one, do you want to add somewhere that it's only for REST?
Thanks, please let me know more about what's missing before we can merge. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.mdand add a warning incore/events.mddocumentations.