Playing around with #Symfony 7 for redoing an old project from scratch. The first 7.0 release will probably be ready when I'm still working on the last migration steps.
At my job I recently worked on a project which had a lot of work with #EasyAdminBundle, and it was an absolute joy to work with. However, after this, there's another joyful moment, and that's logging into #SymfonyCasts and going through the EasyAdmin series.
Just seeing a lot of knowledge I've already gained, and then writing down the gaps so they're easy to remember and I get my knowledge to 100%.
Next project will contain a lot of ApiPlatform. I'm excited 😁
Wow you really have to be careful with #Doctrine and keep an eye on the queries that are happening. The right use of eager loading and being cautious of queries inside of loops is very important.
Also got in-line Form editing working and love it.
One gotcha is that the Form is automatically turned into a FormView when passed to the response. My array of forms had to be manually converted with createView().
🆕 blog! “Doctrine - how to use LIKE with dbal prepared statements”
I'm just getting started with Symfony, so I'm blogging some of the weird things I'm finding. I want to use Doctrine dbal to search a database for a partial match. For example searching for "smith" should find "blacksmith" and "smithy". I have a prepared statement like this: $queryBuilder = $co…
@Edent To help provide a sense of intuition for why it works this way: In the first code snippet, you're putting data directly into your query, which is what DBALs are designed to prevent. You always want your data strictly segregated from your query, to avoid SQL injection vulnerabilities.