Jacob Thomason

Where do we stand on this? It's actually really bad that you can't use proper interfaces with this lib due to these generated base classes. Interfaces end up being loosely...

@mringler it's pretty simple really. You cannot strictly type any interfaces that are implemented by a Propel model, at least for getters/setters defined in the base generated classes. That also...

@mringler Here is an example: ```php

@mringler You're looking way too deep into this. It's really not that complicated. Even methods like: ```php /** * Get the associated ChildAuthor object * * @param ConnectionInterface $con Optional...

@mringler Correct, but it's not just relational getters, like in your example. It's an issue for all getters and setters, since they're loosely typed. And, you don't have control over...

My argument with relational getters is a design decision from Propel/ActiveRecord. It has nothing to do with overriding method signatures, if we really want to get down to it. Obviously...

@mringler BC can be provided with a setting that allows people to stick with loosely typed phpdoc typehints instead of actual real typing. But typing base classes should absolutely be...

`enable_me` is just some `graphqlite-bundle` feature for `login`, `logout` and `me` mutations. It has nothing to do with the actual issue here. If that's solving the problem for you, that's...

I'm assuming this would stand-in for Swift_Mailer's loggers. https://swiftmailer.symfony.com/docs/plugins.html#logger-plugin Does `symfony/mailer` not have any logging and only explicit exceptions? What if you want to log success emails as well for...

@Orgoth We ended up using our adapter service for handling this. It'd have been nice to have provided some more clear direction when Swift_Mailer was dropped, as to what the...