i18n-debug
Ever wondered which translations are being looked up by Rails, a gem, or simply your app? Wonder no more! (by fphilipe)
callstacking-rails
Rails client for Call Stacking - your insurance policy for tracking down those hard-to-find production bugs. (by callstacking)
i18n-debug | callstacking-rails | |
---|---|---|
2 | 6 | |
186 | 40 | |
0.5% | - | |
0.0 | 7.7 | |
over 2 years ago | over 1 year ago | |
Ruby | Ruby | |
MIT License | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
i18n-debug
Posts with mentions or reviews of i18n-debug.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Is it possible to get a list of places i18n.t looks?
We use the i18n-debug gem for that, you might want to check it out: https://github.com/fphilipe/i18n-debug
-
Devise and multilanguages
I would suggest to use something like this gem https://github.com/fphilipe/i18n-debug to debug the lookup of keys that rails is doing. That way you can check exactly what keys you need to translate.
callstacking-rails
Posts with mentions or reviews of callstacking-rails.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-07-14.
-
We need visual programming. No, not like that
We need to see the code paths that were executed for a certain request/feature/transaction.
I created Call Stacking for this visualization.
https://callstacking.com/
-
RoR Debugbar
Very cool project. Similar to the Ruby on Rails debugger that I wrote, which allows you to see all of the methods that are called for a given request (and param values, return values, etc).
https://callstacking.com/
-
For RoR, see in production every method call, parameter and return value
If someone is up for writing a Call Stacking client for the language platform of their choice, please email me.
This would be your reference implementation.
https://github.com/callstacking/callstacking-rails
I'm sure we could work out an arrangement.
- For RoR, see every method call, parameter and return value in production
What are some alternatives?
When comparing i18n-debug and callstacking-rails you can also consider the following projects:
ruby-ray - Easily debug Ruby applications
ifme - Free, open source mental health communication web app to share experiences with loved ones
code-charter - Visual summaries for code repositories
debug - Debugging functionality for Ruby
Sourcetrail - Sourcetrail - free and open-source interactive source explorer