Sorry for adding this with so much little notice. I added that since the 
other one was already present, and that wouldn't change the number of 
implicit dependency on that package.

Obviously not using that class will not trigger any issue, but removing 
that now would be a BC, so I'm against doing that: breaking SemVer would be 
a very bad example here.

I'm all for splitting it into a separate package, but I would like the CC 
input on this, since my previous action seems to be debatable. In any case, 
this would require a 2.0 of psr/log, but I fear that that change would 
scare a lot of people... Even the 1.1 ruffed some feathers!

Il giorno venerdì 7 dicembre 2018 20:23:42 UTC+1, Larry Garfield ha scritto:
>
> On Friday, December 7, 2018 10:19:45 AM CST Rasmus Schultz wrote: 
> > I noticed the introduction of two PHPUnit-specific test-dependencies 
> into 
> > the psr/log package: 
> > 
> > https://github.com/php-fig/log/tree/1.1.0/Psr/Log/Test 
> > 
> > How is this in any way acceptable? 
> > 
> > The dependency isn't even declared in the "composer.json" file - but 
> that's 
> > kind of besides the point. 
> > 
> > First of all, PHPUnit isn't PHP - introducing facilities for a specific 
> > test-framework is extremely opinionated and does not belong in an 
> package 
> > with interfaces designed to bridge projects and provide interoperability 
> > between different frameworks. (PHPUnit being a test-framework.) 
> > 
> > Moreover, these facilities aren't a dependency, at all - you can use 
> this 
> > package just fine without it. There is no rational reason not to package 
> > these dependencies separately. 
> > 
> > These facilities belong in a different package that depends on psr/log, 
> so 
> > you can version them separately. Stuffing these into the package itself 
> is 
> > extremely controversial and could create a serious problem with 
> versioning. 
> > (having to version the interfaces as 2.0 for a breaking change to the 
> > test-facilities!) 
> > 
> > I'm calling for a bugfix release to remove these ASAP. 
> > 
> > Who's even responsible for this? 
> > 
> > There's no issue-tracker on the GitHub project, and I don't see any 
> > discussion about it in this forum. 
> > 
> > wtf? 
>
> One of them has been there for years.  The other was just added recently 
> with 
> little notice. 
>
> This has been discussed before, and frankly I agree that the tests should 
> not 
> be in the package at all.  We have -util packages for this sort of thing. 
>
> Related discussion: 
>
> https://github.com/php-fig/log/pull/52#issuecomment-378323725 
>
> --Larry Garfield

-- 
You received this message because you are subscribed to the Google Groups "PHP 
Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to php-fig+unsubscr...@googlegroups.com.
To post to this group, send email to php-fig@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/php-fig/ed94acf6-698c-4410-8b10-44dba2f40ef7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to