Hey Josh: I think annotate_models is exactly what I'm looking for. Giving it a go can't hurt. :)
Cheers! -Mark On Nov 4, 12:28 pm, Josh Price <[email protected]> wrote: > Does anyone still use the annotate models plugin? > > http://agilewebdevelopment.com/plugins/annotate_models > > It takes your schema and put it as a comment block at the top of your model > classes. Combined with migration-based comments this might work for you. > > When I used this a while back I found keeping it up to date manually mildly > annoying, but if your schema isn't going to change much then it might be a > good solution. > > Josh > > On Wed, Nov 4, 2009 at 12:20 PM, Bodaniel Jeanes <[email protected]> wrote: > > The only problem with that is that a developer may create a migration > >> and forget to update the field descriptions in the model. Out of date > >> and wrong comments are the worst. > > > Good point. Hard to find documentation still sucks though > > >> I like the idea of patching migrations to use the field comment in the > >> database. Then plugins like annotate models could pull the comment and > >> write it to the model file for easy access. > > > If the process of pulling out the value of these fields and displaying them > > somewhere is automatic this scenario would become very useful. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
