Annotate v2.6.0.beta1 Release Notes
-
- ๐ It's now possible to use Annotate in standalone ActiveRecord (non-Rails) projects again.
- โ Adding note that Markdown is actually MultiMarkdown, and recommending the use
of the
kramdown
engine for parsing it. - ๐ Improved Markdown formatting considerably.
- ๐ Bugfix: Needed to use inline-code tag for column and table names, otherwise underscores would cause havok with the formatting.
- ๐ Bugfix: Markdown syntax was incorrect (can't have trailing spaces before the closing marker for an emphasis tag).
- ๐ Bugfix: Remove-annotations wasn't properly finding test/spec files, and wasn't even looking for FactoryGirl factories under the new naming convention.
- ๐ Bugfix: Load the Rakefile from the current directory, not the first Rakefile in our load path.
- โ Added support for new FactoryGirl naming convention.
- ๐ Fix behavior of route annotations in newer versions of Rake that don't spit out the CWD as their first line of output.
- โ Overhauled integration testing system to be much easier to work with, better compartmentalized, and so forth -- at the cost that you must be using RVM to utilize it. (It'll spit out appropriate pending messages if you don't.) Also includes a mode for "tinkering" by hand with a scenario, and won't let you run it through rspect if the repo is in a dirty state. Added appropriate rake tasks to help with all of this.
- ๐ Routes can now be appended, pre-pended, or removed -- and do sane things in all cases.
- ๐ฆ Expose all
position_*
variables as CLI params. - 0๏ธโฃ Make
ENV ['position']
work as a default for all theENV ['position_*']
variables. - ๐ Make rake tasks more resilient to unusual circumstances / code loading behavior.
- Resolve annotate vs. annotate_models ambiguity once and for all by
settling on
annotate_models
andannotate_routes
. This avoids a name collision with RMagick while not needlessly overloading the term. - ๐ Fixed that schema kept prepending additional newlines
- โก๏ธ Updates to make annotate smarter about when to touch a model
- Recognize column+type, and don't change a file unless the column+type combination of the new schema are different than that of the old (i.e., don't regenerate if columns happen to be in a different order. That's just how life is sometimes)
- ๐ Change annotate to use options hash instead of ENV.