Q&A session
summary
Core team answers live Q&A about API Platform 3: the input/output DTO attributes are slated to be removed in favor of serializer-driven schemas and an output: false option for empty responses; data transformers are dropped and migration from 2.6→3.0 requires rewriting transformers/providers and custom controllers often break Platform features. GraphQL support relies on webonyx/graphql-php with no major limitations. A Laravel bridge prototype exists to reuse the core library, and the recent release cycle takes six months versus two years for 2.7→3.0.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:28API Platform input/output options
- 3:40Migration challenges in API Platform
- 8:26Controllers vs API Platform best practices
- 14:09GraphQL limitations and compatibility
- 17:23Laravel compatibility with API Platform
- 22:42Multiple API platforms in monolith
- 26:18API Platform and Laravel integration impact
- 31:58ADR pattern in API Platform
- 34:14Demo project and testing API Platform 3.2
- 37:08Final remarks and Q&A closure
related talks
33mThe journey towards API Platform 3
39mAPI Development in 2017
56mREST or GraphQL? Examples with Symfony and API Platform
30mPanel Discussion: Welcoming V3: Modernizing the Cloud Foundry API
39mAPI Platform — A Daily Tool for (Un)usual Tasks
39mapi-platform
22mDelivering Exceptional Infrastructure as Code through REST and GraphQL
39mSylius & API Platform: the story of integration