Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Does exist some Lint tool for Rails application as a whole?
For example, ruby-lint doesn't see declarations in other modules if modules have been referenced by mentioning them in require clause in application.rb file.
RubyMine also doesn't see them when doing code inspection.
no, there is not.
ruby is a dynamic language, so all you can do in a rails project is to lint syntax in ruby source files with stuff like ruby -v aka ruby-lint.
you can use a tool called rails-best-practices to evaluate your code. but like the name says, it's only best practices and is more soft rules than hard linting.
of course there are many more code analysis tools available like rubocop, they all go into a similar direction.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
What is the best option? I found:
https://github.com/jasonl/eden
http://www.arachnoid.com/ruby/rubyBeautifier.html
but they both seem slightly outdated. Special support for Rails (Knowing which files to format automagically and some other cool things) would be a plus, and a git hook script.
There is RuboCop:
gem install rubocop
rubocop -a
It will also fix all the common mistakes.
Just use vim, in command mode press gg=G
gg - move cursor to the beginning of your file
= - reindent
G - till the end of file
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I've been searching the internet without success, looking for info on acts_as_ferret. The few pages I've found show methods that apparently doesn't exist any more (my rails app show me the "method not found error", and the docs in the acts_as_ferret page are very scarce. Anyone have a good tutorial or API docs about this plugin?
And don't forget you also have the source code. Gemedit is nice for quick viewing of gem source code: http://gemedit.rubyforge.org/
The rdoc is placed in your /ruby/gems/1.8/doc/acts_as_ferret-0.5.2/rdoc/index.html directory by default when you install a gem. This should be correct & current with respect to the version you're using. That's usually the best bet if things aren't current online. It looks like there's some documentation here as well: http://rdoc.info/github/jkraemer/acts_as_ferret, not sure if it's appropriate to the version you're using.
If you have a chance, take a look at http://rubygems.org/gems/thinking-sphinx. It's quite popular and has a good amount of current online documentation.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I am trying to find a simple poll plugin/gem (the type of single question poll that's usually found in site's sidebar). All plugins that I've found are either too complex (like having their own DSL) or they are out of date (i.e. older than couple years).
Does anyone knows a Rails plugin/gem that handles simple polls?
Have you tried SMeRF, I'm currently using Surveyor and yes it is complicated. So I recommend you to use SMeRF, it is a lot more simple. But I can't seem to make it work on Rails3. xP
What version of Rails are you using?
I ended up writing my own custom solution for a simple poll I needed. Unfortunately, I needed it fast so I wrote it within an app I was working on (i.e. I didn't separate it into gem)
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
An open source project called Beast implemented a forum in about 500 lines of Ruby on Rails code. The project seems to have fallen silent (http://beast.caboo.se/). Is there an open source project that replaces beast and is compatible with the database schema defined for Beast? I have used Beast to sponsor a forum and would like to upgrade and move the deployment from Ubuntu to OS X on a more recent version of Ruby on Rails.
Have you looked at altered_beast? Ground-up rewrite of Beast
If you're just looking to obtain the source for Beast, try this SVN tree.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
So I've been using InstantRails to check out Ruby on rails. I've been using Notepad++ for the editing. Now I don't want to install Ruby or Rails on my machine. Is there any walk through/tutorial on how to integrate Radrails or Netbeans with InstantRails?
Here's a tutorial: http://ruby.meetup.com/73/boards/view/viewthread?thread=2203432
(I don't know if it's any good.)
And here's one with InstantRails+Netbeans: https://web.archive.org/web/20100505044104/http://weblogs.java.net/blog/bleonard/archive/2007/03/instant_rails_w.html
I recommend learning Rails and Ruby itself first, and then picking up something like InstantRails. Having too many layers when learning something new can make it hard to know what features are part of which language, and potentially confuse you when trying to determine where a bug is occurring.