-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix generics templates #4
fix generics templates #4
Conversation
30116ce
to
e35882a
Compare
e35882a
to
5730a2b
Compare
@weaverryan i don't think these are my failures |
Hmm, actually, I think they are... it's related to deprecations in PHPStan - so my guess is from the new test. But these are "Other deprecation notices"... are those direct? Indirect? I'm actually not sure - we might need to tweak our |
I guess they are not classified properly because the deprecation is triggered from a class defined inside a phar, so it path has starts with |
I wonder if changing the phpstan dependency to the stable 1.10 in composer.json would help (I can't remember why I have 1.11-dev - probably by accident). |
doesn't help. but i tried using phpunit directly instead of (not-so-)simple-phpunit, and there are no deprecations. |
Yes, but probably just because it's hiding the deprecations :p. Maybe we can just generate and point to a baseline file for these deprecations - https://symfony.com/doc/current/components/phpunit_bridge.html#baseline-deprecations |
3bbdd35
to
cde28fa
Compare
done |
Still not happy - not sure why - phpunit-bridge can be pesky to work with and configure. BUT, I have changed the settings so that if you push, the CI will run automatically vs waiting for my approval 🙃 |
oh yeah, it's hard coded paths in the allowed deprations |
cde28fa
to
ff2153a
Compare
can't see the issue atm. there are deprecations in ci that i don't get locally. |
f8d804b
to
c12df81
Compare
hallelujah |
c12df81
to
15781f2
Compare
Thank you for your hard work on this Ben! |
This PR fixes the templates for
MicroMapperInterface
andMapperInterface
.regression tests have been added.
as an aside, is the
$toClass
param inMapperInterface::load(...)
redundant?It seems we will only ever have concrete implementations here and will just new up a new class, which will match the class provided in the
AsMapper
attribute.