Chapters

20 Chapters | 1:18:30 |

01

The Battle Resource

2:54
02

Designing (Testing) the Create Battle Endpoint

3:56
03

Saving Related Resources in a Form

4:44
04

Finishing the Battle

2:47
05

VirtualProperty: Add Crazy JSON Fields

4:50
06

Form Voodoo: property_path

2:26
07

Adding Battle Validation

3:28
08

EntityType Validation: Restrict Invalid programmerId

5:16
09

HATEOAS & Hypermedia: The Buzzwords Level

4:19
10

Link from Battle to Programmer

2:34
11

The Great Hateoas PHP Library

3:17
12

The HAL JSON Standard

3:53
13

Embedding Objects with Hal?

2:26
14

Customize how your Links Render

4:50
15

Customizing (making less ugly) Embeddeds!

3:44
16

Subordinate URL Structure

3:22
17

Coding the Subordinate Resource Endpoint

3:57
18

Rock-Solid, Consistent Collection Endpoints

4:10
19

Weird Endpoint: The tagline as a Resource?

5:47
20

Weird Endpoint: Command: Power-Up a Programmer

5:50

This tutorial has a new version, check it out!

> APIs > Symfony RESTful API: Hypermedia, Links & Bonuses (Course 5)

Buy Access to Course

13.

Embedding Objects with Hal?

|

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

Login or register to check out the script

2 Comments

Sort By

Login or Register to join the conversation

Chuck norris 8 years ago

Hi,

I have a small interrogation.

In a rest world, what is the best between embed the relation with Hatoeos or Expose the doctrine relation ?

Thanks in advance.

|

weaverryan SFCASTS Chuck norris 8 years ago

Yo Chuck!

Haha, I don't know :). I mean, the "best practice" is to choose a standard - whether it's HAL, JSON API, or whatever - and put make your responses look like they should. For HAL, you're supposed to put things under _embedded. For JSON API, it's different. So, I would say that *if* you find a standard that you really like and are comfortable following, then follow its rules completely. Otherwise, you're kind of "doing your own thing", which is "frowned upon", but happens all the time. And in that case, I like simple structures, so I just exposed the doctrine relation.

I hope that helps! There's still a lot in REST that is subjective. I think we *are* moving towards standards everywhere, but those standards (and the tools that make them easy to use) are still developing.

Cheers!

|

This tutorial uses an older version of Symfony. The concepts of Hypermedia & HATEOAS are still valid. But I recommend using API Platform in modern Symfony apps.

Symfony 3

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": ">=5.5.9",
        "symfony/symfony": "3.0.*", // v3.0.3
        "doctrine/orm": "^2.5", // v2.5.4
        "doctrine/doctrine-bundle": "^1.6", // 1.6.2
        "doctrine/doctrine-cache-bundle": "^1.2", // 1.3.0
        "symfony/swiftmailer-bundle": "^2.3", // v2.3.11
        "symfony/monolog-bundle": "^2.8", // v2.10.0
        "sensio/distribution-bundle": "^5.0", // v5.0.4
        "sensio/framework-extra-bundle": "^3.0.2", // v3.0.14
        "incenteev/composer-parameter-handler": "~2.0", // v2.1.2
        "jms/serializer-bundle": "^1.1.0", // 1.1.0
        "white-october/pagerfanta-bundle": "^1.0", // v1.0.5
        "lexik/jwt-authentication-bundle": "^1.4", // v1.4.3
        "willdurand/hateoas-bundle": "^1.1" // 1.1.1
    },
    "require-dev": {
        "sensio/generator-bundle": "^3.0", // v3.0.6
        "symfony/phpunit-bridge": "^3.0", // v3.0.3
        "behat/behat": "~3.1@dev", // dev-master
        "behat/mink-extension": "~2.2.0", // v2.2
        "behat/mink-goutte-driver": "~1.2.0", // v1.2.1
        "behat/mink-selenium2-driver": "~1.3.0", // v1.3.1
        "phpunit/phpunit": "~4.6.0", // 4.6.10
        "doctrine/doctrine-fixtures-bundle": "^2.3" // 2.3.0
    }
}

Previous Chapter

Next Chapter