Jason Schilling
Jason Schilling
CI is unrelated, just looks like some deprecation messages makes them fail. (IIRC the deprecation message makes PHPUnit return with exit_code != 0)
I came across the same issue, I think that is one of the reasons why the symfony form component has it's own renderer. I have a small workaround, the only...
+1 to Readers and Writers
I came across this issue again and noticed that sluggable is also affected. // EDIT: sorry for close and reopen, wrong button. 😄
Hello @stof this is still an issue, I also noticed some other PR about make it configurable. (https://github.com/stof/StofDoctrineExtensionsBundle/pull/384) Can you please have a look on this?
I don't think this is required anymore?
I don't see any value here as you can easily make them available by make them public in a test config like described in the [symfony documentation](https://symfony.com/doc/current/testing.html#retrieving-services-in-the-test) > The container...
Changed a bit: - Add exports for the types - Update Discover to default export - Add me property - Add broadcast with instance id (Another issue with easier access...
I think the most is covered, but if you can wait several days I will take a look and will improved it.
> Making exports is a good idea, but I think exposing the `me` and the `broadcast` property is not that so. This would make the false impression that you can...