I really really like symfony and api platform. But i have a weird challenge.
(i've never installed anything on a linux machine before, so bear with me please AND i am a newbie to symfony 4).
We have a new Azure server ...
...
//.enableIntegrityHashes()
// uncomment if you're having problems with a jQuery plugin
//.autoProvidejQuery()
// uncomment if you use API Platform Admin (composer req api-admin)
//.enableReactPreset ...
|
var Encore = require('@symfony/webpack-encore'); |
|
|
|
|
|
|
|
if (!Encore.isRuntimeEnvironmentConfigured()) { |
|
Encore.configureRuntimeEnvironment(process.env.NODE_ENV || 'dev'); |
|
} |
|
|
|
Encore |
|
|
|
.setOutputPath('public/build/') |
|
|
|
.setPublicPath('/build') |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.addEntry('app', './assets/js/app.js') |
|
|
|
|
|
|
|
|
|
.splitEntryChunks() |
|
|
|
|
|
|
|
.enableSingleRuntimeChunk() |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.cleanupOutputBeforeBuild() |
|
.enableBuildNotifications() |
|
.enableSourceMaps(!Encore.isProduction()) |
|
|
|
.enableVersioning(Encore.isProduction()) |
|
|
|
|
|
.configureBabelPresetEnv((config) => { |
|
config.useBuiltIns = 'usage'; |
|
config.corejs = 3; |
|
}) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
; |
|
|
|
module.exports = Encore.getWebpackConfig(); |
See Code Block in Script
Provider Transforming Entities to DTOs
... $entities variable is actually a Pagination object. Now that we're
just returning an array, it makes API Platform think that we don't support
pagination.
The solution is dead-simple. Instead of returning $dtos,
return new ...
DTO Class Organization
It took some work - especially getting the update to work before API Platform 2.6 -
but our input & output DTO system is alive! Though... our logic for converting
from CheeseListing to input, input to CheeseListing and ...
Input Data Transformer
... isPublished to false in CheeseListingInput:
Ok, one more time. And... yes! A 201 status code. It worked!
So using a DTO input is a 3-step process. First, API Platform deserializes
the JSON we send into a CheeseListingInput ...
Filter Class Arguments
... $throwOnInvalid
API platform does a cool, but kind of strange thing: if you pass an arguments
option to a filter, it tries to pass that argument - by name - to the
constructor of your filter.
Check it out: in DailyStatsDateFilter ...
Leveraging the Doctrine Data Provider
... getCollection(): it creates a query builder and then loops
over something called the "collection extensions". This is the Doctrine extension
system in API Platform, and these extensions are actually what is responsible
for ...
Calling the Controller View Event
... extensively
inside API Platform. Internally, their controllers return objects. Then, they
have a listener - actually a few that work together - that transforms that object
into JSON, XML or whatever format the user is ...
Bootstrapping a Test Suite
... --env=test:
Repeat that same thing with the doctrine:schema:create command:
Perfect! Next, Api Platform has some really nice testing tools which... aren't
released yet. Boo! Well... because I'm impatient, let's backport those new tools
into our app and get our first test running.
... /api_platform/vendor/api-platform/core/src/Bridge/Symfony/Validator/Validator.php",
"line": 67,
"args": []
},
{
"namespace": "ApiPlatform\\Core\\Bridge\\Symfony\\Validator",
"short_class ...
OAuth with Facebook
... Facebook uses OAuth 2.0 for their API, so we're already dangerous.
And like a lot of sites, they even have a PHP library to help us work with
it. Installing it via Composer is easy. In fact, I already added it to our ...
... /container that we've been working with.This means that when your API Platform code runs, it uses the *same* EntityManager as your test. And so, when your API code, for example, queries for the User object, the EntityManager ...
... .
We use it to add custom endpoints from other bundles, or from the auth system, to add it to the OpenApi dump so it's a neat complete documentation, even filled with endpoints and resources that don't come from API platform.
Since I am upgrading an app from 2.6 to 3 right now, I was wondering about a behavior of the serializer that I ovserved.
In API-Platform >= 3, the default setting in the api_platform.yaml is ...
... collection automatically so that only some are shown, that's not done directly via `security`. Instead, in chapter 35 (will be released this week - but you can peek at it here https://symfonycasts.com/screencast/api ...
... earlier chapter where we even sent a mixture or objects and IRI strings: https://symfonycasts.com/screencast/api-platform/collections-create#sending-embedded-objects-and-iri-strings-at-the-same-time
B) We are using the ...
I have created a Custom Normalizer in my API Platform 3 (Symfony 6) application. The goal of this normalizer is to modify and add some data to the response before returning it to the user (GET collection request). This ...
Hi Gianluca-F!
Ah, apologies for the very slow answer!
Hmm. Yes, what you're expecting makes sense to me! However, it's done this way on purpose: API Platform FIRST loads your data, and THEN applies security. My ...
... the time on API Platform :P).
So, POST worked perfect and as expected.
Now for the GET part, *post-hydration* was the exact word that I was looking for that. I used a Doctrine Listener on PostLoad and worked!, of ...
1015
API Platform
Filter Results