Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A administrate
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • thoughtbot, inc.
  • administrate
  • Issues
  • #542
Closed
Open
Issue created Apr 11, 2016 by Administrator@rootContributor

Remove the FuuBar Gem

Created by: BenMorganIO

I'm currently working through the project in my branch of rails-5-support and trying to get Rails 4.2 to load up RSpec 3.4 and rails 5 to load up RSpec 3.5. However, as the RSpec core version changes, this also changes the requirement of the FuuBar gem.

I'm sure that we can get the gem functional for Rails 5 and RSpec 3.5, but its extra work; especially in future upgrades of Rails and RSpec. Considering this, perhaps it would be OK to substitute a nice loading bar with smaller and easier to manage dependencies.

The FuuBar gem also has an open pull request (https://github.com/thekompanee/fuubar/pull/87) which was submitted back in February. This PR is for RSpec version 3.5.0.beta1, which will most likely conflict with 3.5.0.beta3 which was recently released last week.

FuuBar looks like a great gem though. Heck, I'm probably going to submit a few PRs to it and get it working with Rails 5 and RSpec 3.5 so that I can use it my project. But, from a gem perspective that in the future will have to manage multiple versions of Rails and RSpec, it may not be the best option.

Assignee
Assign to
Time tracking