Skip to content

Describe the fact that first GET collectionOperation is used for resourceClass IRI #407

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Feb 24, 2018
Merged

Describe the fact that first GET collectionOperation is used for resourceClass IRI #407

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
43ba97f
Add note about the fact that first GET collectionOperation is used fo…
Feb 24, 2018
85ae7c3
Update operations.md
dunglas Feb 24, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions core/operations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -485,6 +485,8 @@ automatically instantiated and injected, without having to declare it explicitly
In the following example, the built-in `GET` operation is registered as well as a custom operation called `special`.
The `special` operation reference the Symfony route named `book_special`.

Note: API Platform uses the first operation (with `GET` method) defined in `collectionOperations` to generate the IRI for this resource class. This means that as long as you dont want to overwrite the IRI for this resource class by intention, the default collection operation associated with the `GET` method should be the first operation defined inside collection operations.

```php
<?php
// src/Entity/Book.php
Expand Down