Awesome Open Source
Awesome Open Source

Symfony sample

Tested with testcafe Build Status Scrutinizer Code Quality DeepScan grade Known Vulnerabilities FOSSA Status FOSSA Status


  • You need PHP (7.1+), composer, node (8+ is better) npm or yarn and @angular/cli package installed globally

  • You also need to configure your php with curl and openssl

  • You have to setup the certificates download pem file, put it somewhere on your system and set your php.ini with those values:

    • curl.cainfo = PATH_TO_YOUR_CERTIFICATE/
    • openssl.cafile = PATH_TO_YOUR_CERTIFICATE/cacert.pem

You can run the app with a PHP Built_in server (all npm command relys on it), but some features may not work finely. In fact, Api-platform package rely on some HTTP SERVER features that are not implemented by the PHP Built-in server. So the api indexes like /api/index.json, /api/index.jsonld or /api/index.html will just return a 404 Not Found. There is also the react-admin app generated by the Api-platform that will not work because it relies on api json index.


This application has been realized to get a sample front app with sf3+ & vuejs but it also show basic controllers with what most developpers do : basic controller, controller with twig, http call to external API, logging, API... We will try to not use front manipulation outside of VueJS (the sample with twig are really basic and won't use form per example) Here is how it has been created:

  • composer create-project symfony/skeleton sf-flex-encore-vuejs
  • cd sf-flex-encore-vuejs
  • composer req encore annotations twig api jwt-auth http profiler log doctrine-migrations admin webonyx/graphql-php
  • composer require --dev doctrine/doctrine-fixtures-bundle phpunit/phpunit symfony/dom-crawler symfony/browser-kit symfony/css-selector security-checker roave/security-advisories:dev-master
  • yarn add vue vue-router quasar-framework quasar-extras vuelidate [email protected] graphql apollo-client apollo-link apollo-link-http apollo-link-error apollo-cache-inmemory graphql-tag react react-dom prop-types axios rxjs @devexpress/dx-react-core @devexpress/dx-react-grid
  • yarn add --dev vue-loader vue-template-compiler vue-router react-loader babel-preset-env babel-preset-react sass-loader node-sass [email protected] jasmine karma karma-jasmine karma-spec-reporter karma-junit-reporter karma-webpack karma-chrome-launcher offline-plugin rxjs-tslint
  • yarn install

Then some php controllers has been created on following routes :

  • / : DefaultController with the menu to navigate throught different controllers
  • /demo/simple : SimpleController with route config in routes.yaml and logger injection with autowiring
  • /demo/hello/:name : HelloController with route config in annotations and twig template
  • /demo/http-plug : HttpPlugController to show how to call external API from your controller
  • /demo/login/standard/secured : LoginController for standard login by Symfony
  • /demo/login/json/authenticate : LoginJsonController for json login with JS applications but in stateful context
  • /demo/login/jwt/frontend: LoginJwtController for jwt login with JS applications in a stateless context
  • /demo/vuejs : VuejsController with route config in annotations and VueJS app with specific js/css import
  • /demo/quasar : QuasarController like VuejsController but with the Quasar framework for UX components
  • /demo/form/quasar-vuejs : [Work in progress] authentification with javascript, and a full web application with vuejs and api-platform(rest/graphql)
  • /demo/form/devxpress-angular : Angular7 demo with DevXpress UI components (Datagrid and a Wizard sample with local storage and a sumup zone)
  • /demo/form/devxpress-vuejs : VueJS demo with DevXpress UI components (Datagrid)
  • /api : access ApiPlatform api doc (you need to be authentified from /demo/form if you want to play with it: all entities are configured to be accessed with ROLE_USER)
  • /api/graphql : access ApiPlatform GraphQL implementation (beta release)
  • /demo/api-platform-admin-react : the react admin provided by api platform package (more info here
  • /admin : use the easy admin bundle to allow a comparison between fullstack PHP and PHP/VueJS

And then we followed the documentation here from api platform to create the Admin React tool. We just proceed to some adjustments:

  • we kept only src folder and moved its content at the root of /assets/js/api-platform-admin-react
  • we added the authClient like they did on the documentation
  • on main component componentWillMount() we just do a first fecth on /token to retreive a valid csrf_token for next api calls

But, Vuejs, ReactJS and Angular together ? with Symfony4, WTF ??? Yes it can seems completely stupid to use all this technologies together, but don't forget one thing : this is a POC ! The aim is not to help you to mix all those techs, but just to help you to use some of them finely. The biggest problem in my case is the dependancy management : all those JS libraries may need the same deps but in different version... For instance it seems to be ok, but i think that in future it could be a real brain-teaser.


You can change the php executable (if you want to use a php version with xdebug, or just another version of php) using package.json in the config section. Default php uses the one in path if exists. You can also change the web server port and the asset server port in the same config section.

    "config": {
        "php": "php",
        "server_port_web": "80",
        "server_port_asset": "8080",
        "test_browser": "chrome:headless,firefox"

The test_browser section represent all the browsers you want to use with the Panther testing tool (we previously used testcafe, but it changes toot much and results was not so satisfying).


  • flex: new symfony system to make web dev life easier ; it works with recipes
  • vuejs: top js framework to build SPA, or just widget on classic page
  • quasar: UX component library based on VueJS
  • encore: symfony solution to wrap webpack config and, once again, make your life simpler
  • offline-plugin: webpack plugin to manage offline assets
  • annotations: use annotations everywhere in your PHP code
  • twig: symfony template solution, useless if you don't want to render template with symfony, but usefull to be able to use assets twig helper with webpack encore
  • api: api-platform to build REST api(instead of fosrestbundle)
  • react: js framework used here by api-platform for their react admin component, it's built on top of
  • @devexpress: UX components library for Angular, React, VueJS or VanillaJS, with commercial licence and also an open-source free under some conditions
  • http: a cool library to do http call from http (you could switch it with Guzzle)
  • doctrine-migrations: based on Doctrine ORM, it make it easy to change your db during a project life
  • doctrine-fixture: also based on Doctrine to help you to add fixtures in your DB (for your tests or for project init)
  • ocramius/proxy-manager: i don't directly need it, in fact it's doctrine migrations that needs it. But since the release 2.2, it requires PHP7.2.* and i want this project to be compliant with 7.1 so i force the version of this package until i decide to be only compliant PHP7.2
  • admin: easy admin component to build quick backend with auto form
  • profiler: for debugging purpose
  • log: a logger for symfony
  • security-checker: a tool to check known securities vulnerabilities, to use it, run php bin/console security:check
  • roave/security-advisories: a tool that prevent the install of PHP package from composer with known vulnerabilities
  • phpunit, crawler, browserkit, css-selector: php/symfony task for testing (@todo ll last 3 should be a recipe)
  • panther: the symfony toolkit to manage testing throught a browser (before this compoennt, we had to use npm libraries to control browser)
  • babel-preset-env: do you really need explanation ? this is just for Babel7
  • testcafe: an e2e test framework (might be changed with chimp or anything else, gimme better idea)
  • jasmine & karma: a stack for unit & e2e tests (a more standard stack to replace testcafé)
  • sass: hey, we are not in nineties, we don't write css now
  • bootstrap: the 4th version of the first class css framework (not used with quasar)
  • axios: the library to perform http calls
  • rxjs: THE library to replace the usage of Promise !

Here are some non installed components that may help you:

  • rekit: an IDE for React devlopment, you should install it globally

For Angular (v5), i decided to do quite different way:

  • i initialized a project with angular-cli (first install it globally yarn add -g @angular/cli) like this: cd assets/js && ng new devxpress-angular && cd devxpress-angular && yarn install
  • then i customize the .angular-cli.json to set output path to my root public/dist-ng folder
  • i set this dist-ng folder because encore will remove dist folder when we run some command so with different dist folders i don't have any problem
  • i customize my npm watch scripts and set a new watch:windows which allows to run the 2 watcher (one for encore, and one for angularCli) at the same time with only one npm scripts
  • i decided to not use npm run serve but npm run build with watch options because this last one is the only way to generate files in dist-ng folder. ng serve does everything in memory only


  • clone the project like this git clone [email protected]:Rebolon/php-sf-flex-webpack-encore-vuejs.git and go into this directory
  • install the project with npm run init-project (or init-project:win for windows system) which will launch :
    1. copy the env file (or set them on your system) : cp .env.dist .env
    2. php dependancies installation: composer install
    3. nodejs tooling installation (and angular deps): npm install && cd assets/js/form-devxpress-angular && npm install
    4. assets generation: npm run dev
    5. db init: php bin/console doctrine:database:create & doctrine:schema:create & doctrine:fixtures:load
      • it creates the physical database from the config/packages/doctrine.yaml file
      • it builds the schema based on src/Entity/* files
      • it load fixtures based on a db sample built with calibre software plus a plugin that export data to sqlite format. An alternative to this would have been to use and build yaml fixtures, but i already had an sqlite db so i didn't need this :-)
  • generate certificate for JWT authentification:
    1. Change the value of the key JWT_PASSPHRASE from the file .env
    2. Run npm run jwt-init and use the passphrase you setup for JWT_PASSPHRASE
  • Run your application with php built-in server:
    1. Change to the project directory

    2. Execute the npm run build that will build assets and watch for angular app change

    3. Execute the npm run dev-server-hot (or dev-server-hot:win for windows system) command to start the asset server that will build your assets for vue and react and your manifest.json and serve the assets with hot module replacement when you do a modification on a vuejs file

    4. Execute the npm run sf-dev (or sf-dev:win for windows system) command;

    5. Browse to the http://localhost:80/ URL.

      • Run composer require symfony/web-server-bundle for a better web server.
      • Quit the server with CTRL-C.
      • And launch php bin/console server:start
    6. Run frontend tests with npm run test

Don't forget to prefer an nginx/apache server to be able to use full features of api-platform.

If you want to change default ports, you can use package.json > config : server_port_web for the web server (php built in server), and server_port_asset for the asset server. Default ports are 80 and 8080.

If you update the project:

  • Don't forget to run doctrine:migrations:migrate to take care of DB modifications.
  • Do the following command npm run dump-js-config (or dump-js-config:win for windows system) to create the js config file


Everything is managed by 'encore' symfony package, so have a look at the webpack.config.js and then read their docs

  • npm run dev : will build your assets (in this project it's /public/build/)
  • npm run watch : does the same thing than npm run dev, but it watches files modification to re-generate the assets
  • npm run dev-server : build the manifest.json that map your assets qith their url from the asset server and start a web server that will serve those assets
  • npm run dev-server-hot : does the same thing as previously, but with vuejs framework it also does Hot Module Replacement
  • npm run build : build your assets for production

Take care, the asset server listen to port 8080 so don't start your main server on that port, or specify another port for the dev-server using --port 9999 for example

Also, if you want to use the asset server finely, you have to add the assets configuration in the config/packages/framework.yaml file : json_manifest_path: '%kernel.project_dir%/public/build/manifest.json'. In fact the npm command will build asset in memory only, and modify the manifest file to map asset to a new url served by the asset server instead of the main web server.

In the main layout, we load 3 common files: manifest.js, vendor.js and service-worker.js. Vendor is where you wan put all common libraries used on almost all pages. The source file for this bundle is assets/js/app.js. SW is for the service workers. It's default behavior is to manage the Cache file. You can have a look at offline-plugin for webpack.

code quality


The project uses 2 packages to lint and fix the code style of PHP code :You can install phpcs to check your code

  • squizlabs/PHP_CodeSniffer to lint and follow PSR1/PSR2 rules.
  • friendsofphp/php-cs-fixer to fix the code

Lint with this command vendor/bin/phpcs src -n --standard=PSR1,PSR2 --report=summary to get a summary of errors. You can fix it with vendor/in/phpcbf src -n --standard=PSR1,PSR2 which is delivered with phpcs, but it doesn't fix everything so i suggest to use php-cs-fixer with this command vendor/bin/php-cs-fixer fix src [email protected],@PSR2


For Javascript the following packages has been used: npm install prettier

To lint the code: node bin-prettier.js assets/js/** To fix it: node bin-prettier.js assets/js/** --write


For PHP you should configure your IDE to follow PSR1/PSR2 code style (or anything else if you prefer). For JS you will have to install prettier tool.


On PHP we use PHPUnit and Symfony web testcase. For Javascript, we decided to work with testcafé. We have basic tests on PHP that will try to test that we have HTTP 200 OK on each routes. We should also tests Commands and other classes, but we should also test more finely the API content. Take care with Symfony4 to configure the config/packages/test/framework.yaml file to overload the session.storage_id with a mock !

JWT Certificates in test mode, we don't use pem files from your dev/prod env. In fact we use pem files generated specifically for tests and copied from var/travis/config to var/cache/config

On Javascript we have unit and e2 tests. Units tests are managed by jasmine and karma. It allows to test function, class, component. For e2e tests we use testcafe from devExpress. It allows to launch browsers and drive them by code to reproduce a human behavior. Here the tests runs on a chrome headless, and firefox but you can configure it in the package.json file in the config.test_browser node. We now use Panther to run e2e tests. It's automatically ran when we run phpunit commands.

npm run test-karma will run js test and will generate a karma_report.xml files in the following folder /var/report/.

If you wonder how to tests your VueJS components, you can hae a look at this website which describe a lot of tests. Sadly it's in french !

In this application i used Karma for one application with VueJS (in /assets/js/vuejs). And i used Panther to test pages fully generated by Symfony. Karma is configured with assets/tests/units/karma.conf.js !


On PHP i use those 2 packages to prevent the use of deprecated packages or with vulnerabilities:

  • security-checker: when you run php bin/console security:check it will checks your dependancies vs known vulnerabilites. You should use it on existing project.
  • roave/security-advisories: it will prevent the composer require and update command on package with known vulnerabilities. But it won't prevent the composer install with an existing composer.lock so you are safe to deliver existing project.

On JS i use snyk services.

@TODO finish on PHP and JS checks + tools to audit the code + software that analyse sql/xss/file injection, csrf, ... @TODO explain the usage of tools like OWASP ZED, sqlmap, php avenger... @TODO help to setup security system: stateful app = take care at csrf ; stateless app = should i use jwt, api key, OAuth, anything else ?

Don't forget to use HTTPS, even in local to help you find errors that will happen in production. One certificate has been generated for localhost (with and is available in /var/certificates/.cert|.key There is a simple nginx conf (used for travis CI) that use those certificates so you can use nginx to work (just don't forget to change the port that is fixed to 80 like setup in the package.json).

TestCafé for functional testing generate an error when you don't use ssl: Uncaught (in promise) DOMException: Only secure origins are allowed (see: But for instance i didn't found any solution to run it finely without --skip-js-errors parameters.

Symfony security

In Symfony i configured different firewalls:

  • security_js and security_php share the same context so when you are logged on one, you are also logged on the other. I did this because a firewall cannot use both form_login and json_login (or i didn't found the way), and i wanted you to understand the concept of context.
  • security_jwt is for stateless app. You can read the following tutorial to understand

If you doesn't need JWT, you can use ApiKey pattern. For this you have to implement the required Authenticator: If you need more tuning with huge APIs, you may require OAuth with JWT. OAuth will help you so have a look at this website:


In statefull app you will have HTTP Cookies. Even if you don't really manipulate them, and that they are used only to transport the sessionId between the server and the client. But if you use them to store other informations, you should be aware that they can be misused and that they can open XSS or CSRF web fail. Your cookies must have some specific attributes:

  • secure
  • httponly
  • date (to prevent them to be infinite)
  • samesite (strict or lax...)

You have to pay attention at them. And you can play with them on those sites: and (source here: and related talk here:


Take care at the custom listeners that you could write based on Api-Platform documentation. They are used by all controllers, not only those from ApiPlatform.


In /api you can test the API with the swagger interface. Because the route uses JWT token you have to call the /demo/security/login/jwt/tokens route with HTTP POST and Basic Auth. Login is test_php or test_js and password is test ! Then in the swagger interface click on the upper right button Authorization and add 'Bearer THETOKENRECEIVED'

To get a valid JWT token you could use the login jwt route: /demo/login/jwt/frontend But, because i'm cool ;-) i made a command that will provide you the token. So just do php bin/console app:new-jwt-token and it will return a token. You can also provide a username/password to the command, i let you read the help of the command to know how-to do.

When using GraphiQL with secured resources, you won't be able to provide any token (i didn't find any clue for this). So i found this good tool to query my API by providing required Authorization header:


If you want to allow sorting based on columns, you will have to add Filter annotations on Entity. Look at the Book entity and its ApiFilter which allow to sort on id and title. Then you will be able to call the api like this: http://localhost/api/books?order[id]=DESC


Sometime you will want to filter on some fields: i want Reviews published after xxx. For things like this you have to add new ApiFilter (like we did with sort). There is a sample in the Review entity

You can also filter on relation, but in that case you will have to use the id (or the iris) of the relation as the value of the filter. More information in documentation of ApiPlatform.

Normalizer, or how to return data from nested entities

At the beginning when you query a Books route, each nested entities like Editors, Series, Authors will be represented only by IRI like : "/api/serie/1" This is cool when you don't need all nested information, you will prevent the user to download too many data. But very often, your application will require those informations, and in that case you seem condamned to do further HTTP call to retrieve all sub entities.

You are on the wrong way, and i was too !

Test the route /api/books and you will retreive that kind of response:

    "id": 1,
    "title": "20th Century Boys (Deluxe), Tome 1 test",
    "description": null,
    "indexInSerie": 1,
    "authors": [
        "id": 1,
        "role": {
          "id": 1,
          "translationKey": "JOB_WRITER"
        "author": {
          "id": 1,
          "firstname": "Urasawa"
    "editors": [
        "id": 1,
        "publicationDate": "0101-01-01T00:00:00+00:09",
        "collection": null,
        "isbn": "",
        "editor": {
          "id": 1,
          "name": "Panini Comics"
    "serie": {
      "id": 1,
      "name": "20th Century boys (Deluxe)"

You can tell your API to return those nested entities. Look at Book and Serie entities. You will find extra annotation with @Groups and attributes. In Book, look at the main annotation, and at related property (i only show title property but more are aimed by @Groups, look at original code here:

 * @ApiResource(
 *     ...
 *     attributes={
 *          "normalization_context"={
 *              "groups"={"book_detail"}
 *          }
 *     }
 * )
 * @ORM\Entity
class Book implements LibraryInterface {
     * @Groups("book_detail")
     * @ORM\Column(type="string", length=255, nullable=false)
     * @Assert\NotBlank()
     * @Assert\Length(max="255")
    private $title;

And now the Serie entity, wher you only need to add @Groups on the properties you want to be returned:

     * @Groups("book_detail")
     * @ORM\Column(type="string", length=512, nullable=false)
     * @Assert\NotBlank()
     * @Assert\Length(max="512")
    private $name;

Have a look at Kevin Dunglas slides because it gimme some clue for this feature: His talk may be online in future but i don't kno when ;-) so here is the page that may link to the video, on day:

I still need to work on this feature because it would be cool to be able to build different route that may return IRIS or Normalized data. I don't know if it's possible and maybe i should go to GraphQL API because that's its job to do that kind of thing with its "Query".

Custom Route

There is a sample of custom route based on Action Demand Responder pattern that will allow to create new Books and it's dependancies in one HTTP call. You won't need to create sub-entity before creating the main one, said the book. The endpoint is /api/booksiu/special_3 [POST]. It takes the following JSON string as Body:

// The most complete sample, with de-duplication of editor (only once will be created)
    "book": {
        "title": "Zombies in western culture",
        "editors": [{
            "publication_date": "1519664915",
            "collection": "printed version",
            "isbn": "9781783743230",
            "editor": {
                "name": "Open Book Publishers"
        }, {
            "publication_date": "1519747464",
            "collection": "ebooks",
            "isbn": "9791036500824",
            "editor": {
                "name": "Open Book Publishers"
        "authors": [{
            "role": {
                "translation_key": "WRITER"
            "author": {
                "firstname": "Marc",
                "lastname": "O'Brien"
        }, {
            "role": {
                "translation_key": "WRITER"
            "author": {
                "firstname": "Paul",
                "lastname": "Kyprianou"
        "serie": {
            "name": "Open Reports Series"

// This one re-use database information for editor / author / job / serie
    "book": {
        "title": "Oh my god, how simple it is !",
        "editors": [{
            "publication_date": "1519664915",
            "collection": "from my head",
            "isbn": "9781783742530",
            "editor": 1
        }, {
            "publication_date": "1519747464",
            "collection": "ebooks",
            "isbn": "9782821883963",
            "editor": {
                "name": "Open Book Publishers"
        "authors": [{
            "role": 2,
            "author": 3
        }, {
            "role": {
                "translation_key": "WRITER"
            "author": {
                "firstname": "Paul",
                "lastname": "Kyprianou"
        "serie": 4


  • [x] setup Sf4
  • [x] setup symfony/webpack-encore
  • [x] db: add a model with doctrine entities
  • [x] db: add db fixtures at init! and fixtures for test only: done with the DoctrineFixturesBundle, it will generate fixtures based on var/data/fixtures.db, and when called from test env it will build a small scope of fixtures
  • [x] api: configure ApiPlatform
  • [x] api: setup one custom route for ApiPlatform
  • [x] api: replace IRIs for nested entities by real data (normalizer usage)
  • [x] api: setup custom route with nested objects on create/update/read (read should be solved ith serializer, create/update might be solved with custom route or DTOS so try 2 ways)
  • [ ] api: those custom route must referenced by the API documentation on /api route with correct description (for instance it's just book: string ...)
  • [x] api: use normalizer to get nested entities
  • [ ] api: use denormalizer to post/put nested entities (and use custom route when we want deduplication for example)
  • [ ] api: use properties in queryString to select only wished props from REST: api/books/1?properties[]=title&properties[]=serie
  • [x] api: improve JSON error from custom route: for instance when editor is misfilled it just return this message (without property path): jsonOrArray can be string or array
  • [ ] api: graphQL: multiple queries in one call ?
  • [ ] api: graphQL: multiple mutations in one call ?
  • [ ] api: graphQL: how to mutate nested objects in a minimal call ?
  • [X] api: check best security system to setup with ApiPlatform (JWT / ApiKey / cookie & csrf system but in that case we are stateful which is not cool for deployment and replication ?). Finally we use JWT which is the best thing to do and compliant with statefull or stateless.
  • [ ] api: JWT setup the pattern for the refresh-token or anything else more info here : when getting a 401 from api it should tells more information: does the token is valid or not ?
  • [x] front: setup VueJS
  • [x] front: use Quasar with VueJS
  • [x] front: move on Quasar 0.15.x
  • [ ] front: move on Quasar 0.17.x
  • [x] front: move on Angular 6 with HttpInterceptor, Guards, SSR
  • [x] front: Angular6 with prod build, the assets (js/css) are not wel loaded coz they are generated with versoning hash whereas the twig template load them in hard without hash (no manijest may help the asset helper)
  • [x] front: Update to Angular7
  • [ ] front: improve bundle size for Angular (for instance there is a 4.7Mb vendor.js file which may be devxtrem full deps whereas we use only some widgets)
  • [x] front: move on Devxtreme 18.x and use it with VueJS
  • [x] front: setup CSRF protection with VueJS app
  • [ ] front: migrate app 'form-devextrem-angular' to angular6 when there will be compatible (this thread may helps:
  • [x] quality: setup unit tests for JS (karma/jasmine)
  • [x] quality: setup e2e tests for JS (testcafé)
  • [x] quality: setup phpunit tests for PHP (unit test and webtestcase)
  • [x] quality: write some JS units tests
  • [x] quality: write some JS e2e tests
  • [x] quality: write some PHP tests
  • [ ] quality: fix testcafe role where sometimes they are not played:
  • [x] quality: setup tests reports
  • [x] security: setup security with Symfony (ticket open coz i get 500 instead of 403: Still WIP at this time) and choose between cookie (stateful), JWT (with Lexik bundle) or ApiKey ( : I implement both statefull and JWT samples, but i didn't take the time for ApiKey
  • [x] back: setup EasyAdminBundle
  • [ ] back: improve EasyAdminBundle with custom screen
  • [x] back: setup React Admin from ApiPlatform (take care at this issue is mandatory
  • [ ] back: fix React Admin Book creation: it allows multiple authors (projectBookCreation) whereas it should not, and try to display the name of the author/editor... instead of their iris which is unundertandable
  • [ ] back: customize React Admin to display more information on datagrid, and customize form in book edition per example
  • [ ] back: keep EasyAdminBundle or React Admin: make a choice coz both are doing the same, i need to measure differences, and also the ease to do custom screen (change forms, manage rights...)
  • [ ] front: create another route with VueJS that use GQL instead of REST
  • [ ] front: add storyBook package for VueJS and Angular and use it to manage and test our components
  • [x] quality: code style: use phpcscbf instead of php_cs_fixer coz it's embeded with phpcs and it uses the phpcs config file: I decided to keep php_cs_fixer because it's more complete!
  • [ ] quality: transform this project into a meta package that will install all requirements for JS app within Symfony (like does laravel)
  • [x] security: check if i need the JMSSerializerBundle or if the serializer component is enough (if autowiring runs well, why not): I prefer to use Symfony serializer, it's enough
  • [ ] db: have a lookAt the HauteLookAliceBundle to help in the creation of real fixtures during tests (instead of generating a new test.db which could be long)
  • [ ] api: try instead of ApiPlatform to try nested query/mutations (resolver are not auto-generated)
  • [ ] quality: use a server logger for both JS and PHP (and also maybe HTTP, DB, MessageQueuing, ...), it will helps to improve quality of the app by identifing users system/browser and most current errors (Sentry or other service must be tested
  • [x] front: move on babel 7 with babel-preset-env (remove all related babel from readme and read for more info on update)
  • improve this tutorial with an API Route built with Api platform (without DB) and install the vue-generator from api-platform for a crud sample
  • manage Entity orphanRemoval / CASCADE onDelete
  • find a good way to add a pre-commit hook that lint PHP and JS code, and run the PHP / JS tests
  • Here is a sample of GraphQL query with 2 queries in one call but i don't know how to manage this with Vue-apollo (he can't accept this coz it maps the result to the data[nameOfapolloQuery] whereas i have 2 names...) ? IN FACT the solution is the result hook (see, and the documentation)
query getBooksAndSerieQry($firstBook: Int, $afterBook: String, $firstSerie: Int, $afterSerie: String) {
    getBooksAndSerie: books(first: $firstBook, after: $afterBook) {
        edges {
            node {
        pageInfo {
    getBooksAndSerie: series(first:$firstSerie, after: $afterSerie) {
        edges {
            node {
        pageInfo {

extras info

I wrote some articles on medium to explain some practices setup in this project:

third party issues that helped me to go on

Third-part licencing


FOSSA Status

Get A Weekly Email With Trending Projects For These Topics
No Spam. Unsubscribe easily at any time.
javascript (67,431
php (15,838
react (5,043
angular (1,237
webpack (1,106
vuejs (1,050
reactjs (1,003
bootstrap (629
symfony (451
sass (437
npm (412
doctrine (60
single-page-app (59
e2e-tests (34
quasar-framework (22

Find Open Source By Browsing 7,000 Topics Across 59 Categories