Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete Rewrite for Rails 3/4 & Ajax #53

Open
wants to merge 346 commits into
base: master
Choose a base branch
from

Conversation

pboling
Copy link

@pboling pboling commented Sep 13, 2012

NOTE: @brynary and I have discussed and agree that we'd like to merge the projects rack-bug and rack-insight together.

I forked LogicalInsight (which was a substantial rewrite itself) and rewrote it to be much better. We are moving towards a kick-ass merger/migration between the venerable Rack::Bug and the new Rack::Insight. Spec suite has also been updated!

My next major goal is to spit each panel out into it's own gem so the panel's dependencies can be managed separately, since they are very version specific, and there is no need for /rack-(bug|insight)/ to be tied down to dependencies of dependencies. Rather panels should support a specific, versioned, /rack-(bug|insight)/ panel API.

pboling and others added 30 commits March 8, 2015 14:36
Implement EnableButton and Toolbar with Rack::Toolbar;
Extract PathMatchFilters to mixin;
Add specs for EnableButton and Toolbar;
Remove specs that are pushed to Rack::Toolbar
d3cfc5a introduced a `warn` statement that prints when redis is not available.

This gets printed whenever the rails environment gets loaded (so, `rails s`,
`rails c, `rake`, etc) which is a bit annoying. The output also broke some
specs in a project that was checking the stdout of some of our
scripts.

@pboling suggested there's a better implementation in http://git.io/vfGPX
Remove log output when redis isn't loaded
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet