Andrew W. Lee

@Z2Flow Sorry for the delay, I had a time to take a look. Adding support for multi-line column comments should be okay, did you have an example migration you could...

@Z2Flow apologies for the delay, I have some time now so I'm back to working on multi-line comments. Can you check for me how `\n` (line breaks) are stored for...

As an update, I did take a look at this yesterday. The changes required were more extensive than I originally thought, so for the time being I'm not going to...

I am going to close this ticket for now since there hasn't been activity in some time, however feel free to re-open. I'm just doing some tidying.

Taken from https://github.com/ctran/annotate_models/pull/892 > Given a Rails application with multiple databases, tables in two databases with the same table name, and corresponding models with different names, some files get annotated...

The issue lies in building the list of related files for a model file. Using the example Rails project https://github.com/cygnuseducation/annotate-test-app, running `bundle exec annotaterb models` consecutively led to the same...

Note for any future viewers, the change may require Rails 6+ support as the behavior for `#connection_specification_name` changed between Rails 5 and Rails 6.1. https://apidock.com/rails/v5.0.0.1/ActiveRecord/ConnectionHandling/connection_specification_name https://apidock.com/rails/v6.1.3.1/ActiveRecord/ConnectionHandling/connection_specification_name

TODO: Check how this interacts with `:include_version` option set, as it currently caches the version. In a multi database setup, it _looks_ like it's possible for each database to have...

I currently don't have time for this, so if any future viewer wants to take this on feel free. Closing this PR for now.

Change configuration from exclusion model to inclusion model, more context in issue #103. - Would want 5.0 to have deprecation warnings, followed by exclusion options to be removed in 5.1+