Chapters

27 Chapters | 2:54:11 |

01

API Platform Installation!

6:42
02

Our First ApiResource

5:37
03

Swagger: Instant, Interactive API Docs

8:32
04

OpenAPI Specification

6:32
05

JSON-LD: Context for your Data

10:30
06

Hydra: Describing API Classes, Operations & More

6:01
07

API Debugging with the Profiler

3:17
08

Operations

5:21
09

The Serializer

9:13
10

Serialization Groups

9:34
11

@SerializedName & Constructor Args

7:15
12

Filtering & Searching

6:02
13

PropertyFilter: Sparse Fieldsets

5:34
14

Pagination

4:34
15

More Formats: HAL & CSV

6:05
16

Validation

6:29
17

Creating the User Entity

5:07
18

User API Resource

7:20
19

Relating Resources

7:38
20

Relations and IRIs

4:39
21

Embedded Relation

7:54
22

Embedded Write

8:22
23

Adding Items to a Collection Property

4:38
24

Creating Embedded Objects

7:06
25

Removing Items from a Collection

5:29
26

Filtering on Relations

5:06
27

Subresources

3:36

This tutorial has a new version, check it out!

> Symfony 5 > API Platform 2 Part 1: Serious RESTful APIs

Buy Access to Course

14.

Pagination

|

|

Autoplay

Keep on Learning!

If you liked what you've learned so far, dive in! Subscribe to get
access to this tutorial plus video, code and script downloads.

Start your All-Access Pass

Buy just this tutorial for $12.00

Previous Chapter

Next Chapter

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Login or register to check out the script

2 Comments

Sort By

Login or Register to join the conversation

Eric 6 years ago edited

In order for a client application, that is consuming a Hydra formatted JSON response, to know what the last page number is they would need to parse the "page" query parameter off the "hydra:last" string, correct?

Example: using this format it would be very easy to have pagination links to the next and previous pages. But if a client application wanted to show more page numbers available (ie: linking to pages 1, 2, 3 .... 5, and 6) they would need to parse the "page" query parameter, determine that the last page is 6 and build the links from there, correct?

Just making sure this is suggested approach as I've always passed something like the "lastPage": 6 in a JSON response containing paginated results.

Thanks!

|

MolloKhan SFCASTS Eric 6 years ago edited

Hey Eric

I think your approach is correct. You will have to read the last key value and build your pagination table dynamically

Cheers!

|

This tutorial works great for Symfony 5 and API Platform 2.5/2.6.

Symfony 4 API Platform 2.4

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.1.3",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "api-platform/core": "^2.1", // v2.4.3
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // 1.10.2
        "doctrine/doctrine-bundle": "^1.6", // 1.11.2
        "doctrine/doctrine-migrations-bundle": "^2.0", // v2.0.0
        "doctrine/orm": "^2.4.5", // v2.7.2
        "nelmio/cors-bundle": "^1.5", // 1.5.5
        "nesbot/carbon": "^2.17", // 2.19.2
        "phpdocumentor/reflection-docblock": "^3.0 || ^4.0", // 4.3.1
        "symfony/asset": "4.2.*|4.3.*|4.4.*", // v4.3.11
        "symfony/console": "4.2.*", // v4.2.12
        "symfony/dotenv": "4.2.*", // v4.2.12
        "symfony/expression-language": "4.2.*|4.3.*|4.4.*", // v4.3.11
        "symfony/flex": "^1.1", // v1.21.6
        "symfony/framework-bundle": "4.2.*", // v4.2.12
        "symfony/security-bundle": "4.2.*|4.3.*", // v4.3.3
        "symfony/twig-bundle": "4.2.*|4.3.*", // v4.2.12
        "symfony/validator": "4.2.*|4.3.*", // v4.3.11
        "symfony/yaml": "4.2.*" // v4.2.12
    },
    "require-dev": {
        "symfony/maker-bundle": "^1.11", // v1.11.6
        "symfony/stopwatch": "4.2.*|4.3.*", // v4.2.9
        "symfony/web-profiler-bundle": "4.2.*|4.3.*" // v4.2.9
    }
}

Previous Chapter

Next Chapter