Bodaniel Jeanes wrote: > Ultimately if the purpose is for documentation, it should be somewhere that > developers will expect to find documentation: the README, the doc/ > directory, or in comments in the code (such as in the model that it is > relevant to).
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. 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. -- James Healy <[email protected]> Wed, 04 Nov 2009 12:11:46 +1100 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
