Describe the problem
wisper 2.x, which is a dependency of tty-reader, mistakenly publishes its internal bin/console script as a gem executable. That means that installing tty-reader can result in a warning like this:
wisper's executable "console" conflicts with graphql-rails_logger
Overwrite the executable? [yN]
How would the new feature work?
The bin/console executable was removed in wisper 3.x, but this fix was never back-ported to 2.x. Therefore, to take advantage of the fix, tty-reader.gemspec needs to be updated to use wisper 3.x.
There is already a PR open: #32
Drawbacks
If there are incompatibilities between wisper 2.x and 3.x, this change may affect consumers of tty-reader.
Describe the problem
wisper 2.x, which is a dependency of tty-reader, mistakenly publishes its internal
bin/consolescript as a gem executable. That means that installing tty-reader can result in a warning like this:How would the new feature work?
The
bin/consoleexecutable was removed in wisper 3.x, but this fix was never back-ported to 2.x. Therefore, to take advantage of the fix,tty-reader.gemspecneeds to be updated to use wisper 3.x.There is already a PR open: #32
Drawbacks
If there are incompatibilities between wisper 2.x and 3.x, this change may affect consumers of tty-reader.