New `ignore_multi_database_name` option seems to be non-functional

[RoseAndres]

Running rails db:migrate on our codebase with the new-ish setting ignore_multi_database_name: (added by 8ec1d844ad0ea92f7305f25e7972153d95bc6b83) set to false true in our .annotaterb.yml does not prevent the database_name from being populated in our model annotations.

[OdenTakashi]

Hi @RoseAndres

Thanks for the report.

ignore_multi_database_name: false means that the database name is not ignored, so it will be included in the annotations.
To prevent database_name from being populated, the option needs to be set to true.

[OdenTakashi]

@RoseAndres
How is this issue going for you since then?

[RoseAndres]

@OdenTakashi My apologies, I typo'd (fixed in original post now). I was attempting to run the migrations to update our model annotations, with a value of true for the ignore_multi_database_name: setting. I had it commented out in our .annotaterb.yml and retried just now with the same result (database name still being populated).

[OdenTakashi]

@RoseAndres
Sorry I should have asked this earlier.

The ignore_multi_database_name option has not been included in a released version yet, so if you are using a released version of annotaterb, the setting may not take effect even when set to true.

Could you please let us know which version of annotaterb you are currently using?

[RoseAndres]

Ahhhh that'd probably do it, huh? 😅

Looking in our gemfile.lock, it looks like we're on 4.20.0.

[OdenTakashi]

@RoseAndres
Thanks for checking!

That explains it — ignore_multi_database_name isn’t included in the released versions yet, so it won’t work on 4.20.0.
Glad we were able to figure out the cause.

Please wait for the next release.

[bryan-ash]

@OdenTakashi I'd love to see this in a release ... we have 1534 model files being updated with the database name, when we don't need.