Should this package be called "Fake Except" instead?

[drbyte]

Calling it "laravel-event-fake" suggests that this adds Event::fake ... but it doesn't.

Don't get me wrong! I like what this package does -- I have a project I'll try it out on this weekend!
I just felt like "when I see this in my composer.json I know I'm not gonna remember that it actually means laravel-event-fake-except

[BrandonShar]

In short, I think you're right.

I didn't name it that originally because I was considering ita Laravel Event::fake enhancement, which was probably getting ahead of myself since it only has two additional functions both related to "fake except".

So, I do think your name makes more sense, but I'm not sure how to rename a package in a non-breaking way.

[drbyte]

Depends how many installs. Looks like 25 right now.

On packagist, I've never renamed a package myself, so I'm not sure if they'll handle the rename for you. But I do know you can mark it as abandoned. Then update your github repo to the new name, update your composer.json with the new name, and submit the new package on packagist.

[neodisco]

Just wanted to say thank you for this package. It's exactly what I'm looking for - the ability to test a specific event and listener without worrying about triggering anything else. Perfect and thank you! I agree "Fake Except" would be a better name.