James Titcumb
James Titcumb
Aye yes this is a really good idea: use context to figure out how to continue. At the moment we simply bail out of the evaluation, but if we know...
If we work on the assumption only a `git` rename is detected, and that PSR-0/4 is used (analyse `composer`) it could potentially work (mostly spitballing so there may be a...
Is it really in the scope of BCC to make sure all the deps are there? I'm leaning to "no", and I'm not a fan of the stubbing idea either....
That's acceptable I think... Or maybe simply collect errors and display at the end? Thinking a summary output like phpunit/phpcs like: ``` .......B......E...... .....B............EEE ``` Where `B` is a break...
(not necessarily add the output, was just an example btw)
to be clear: I think the stubbing should be removed; it should be a hard fail like @maglnet said: > `did you check your dependencies?` and give a hint to...
YAML seems like a great idea :trollface:
Maybe make it an option? `--compare-against-latest-patch`, `--compare-against-latest-minor`, etc.?
> merging a red PR from a contributor will lead to all subsequent PRs going red, until a new minor release is cut Yes, I observed this where I'm using...
@lisachenko I'm planning on creating an adapter to make this possible, see Roave/BetterReflection#18