annotaterb icon indicating copy to clipboard operation
annotaterb copied to clipboard

A Ruby Gem that adds annotations to your Rails models and route files.

Results 69 annotaterb issues
Sort by recently updated
recently updated
newest added

This issue is part of the work for issue #188. > Given a Rails application with multiple databases, tables in two databases with the same table name, and corresponding models...

Hi @drwl ! Hope you're doing well. Long time no chat :) Thanks for helping maintain this gem moving forward for Rails 8. I was wondering if we can add...

I have a class that was written: ``` # Schema information from previous annotator module SomeModule # Some doc about MyModel class MyModel < ... ``` I changed all of...

The old gem would leave my class doc where I put it - right before the class: ``` # Schema information # ... # My doc about MyModel class MyModel...

#### Description When I create a database migration file that contains a new column with `comment:` containing Japanese characters and execute it, the annotations corresponding to that column should be...

**Description** Currently, `annotaterb` provides annotations for models and routes of a Rails application. It would be incredibly useful to have a dedicated command (e.g., `annotaterb controllers`) that automatically inserts comments...

## Prelude This feature was implemented by me in [annotate_models](https://github.com/ctran/annotate_models) in those PRs: [#988](https://github.com/ctran/annotate_models/pull/988) and [#999](https://github.com/ctran/annotate_models/pull/999). Since that other GEM does not seem to be maintained anymore, I am considering...

enhancement

Hey -- we're updating from annotate to annotaterb and because of some non-standard stuff it's causing a problem in our tests because the old annotate gem has activerecord as a...

This would be a good enhancement that automatically enforces that annotations are up to date if people run `db:migrate` in a CI system! The `CI` env var is set when...

I can't see a reason not to load defaults when initialising an Options object (and the comment on line 158/96 suggests it's desired behaviour), so this calls `load_defaults` during init...