Skip to content

Potential technical overhead by adding RSpec to the gem? #1

Description

@andreip1

gem "rspec", "~> 3.0"

I came across this project and I was ready to pitch it to my CTO, but I'm not sure it's in the right state.

Could I suggest removing rspec as it implies the need to test, and consequentially, of doing something which I feel it's against passive_queue's ethos.

What do you think?

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions