Keeping track with Annotate Discussion
Some time ago I had issues with the `annotate` gem - specifically with auto-annotating models after a `db:migrate` and with some PostgreSQL-specific datatypes (annotate just failed on these). So I wrote an alternative - https://github.com/7even/ac..., it uses the ActiveRecord schema dumper so it can annotate everything you can see in your `db/schema.rb` in the same familiar syntax (both table fields and indexes). It doesn't annotate neither routes nor unit tests though because I didn't need those.
FYI...I had to run "bundle exec annotate" I'm using rails 4.1.4 and ruby 2.1.2.
I've installed annotate on Rails 5,but I noticed when I run the g annotate:install that it creates a .rake file. Is it ok to use this on rails 5, because as far as I know the rake is depricated and use rails instead
Rake isn't deprecated, they just added a way for you to call it with the rails command so it's less confusing when to use rake vs rails commands. It still functions exactly the same, just simpler now. 🙌
Yep, shouldn't have a problem. You can always check out their GitHub if you run into issues.
Personally, I think it makes more sense to just get a GUI for your database and keep the model files clean and concise. With postgres, Postico is awesome and PSQL (a free option) is also very good.
Great content, really helpful. Here is my thought on the gem - https://www.inkoop.in/blog/how-to-use-annotate-gem/.
Anyone having issues with the command 'annotate' not working in the command line after following this tutorial?