Naoki Kodama

Hi @Gruntfuggly , Is there anything I can do to assist to get this fix merged into todo-tree? Please let me know - I'm happy to help in any way...

@drwl Please review this whenever it’s convenient for you. :pray:

@drwl Thank you for checking 👍 Since it's your gem, please consider this just as a reference. > Currently, I make a branch with the new version history so I...

Hi @wmakley Have you tried using the `--nested-position` option? It should make the annotation appear directly above the nested class (Action) instead of inside the module.

@sirwolfgang Thanks for checking and confirming! It might be that the existing annotation isn’t indented properly, so when it’s updated, the indentation isn’t applied. Could you try running the following...

It does look like there is an issue specifically in the *update* flow — I can reproduce the indentation breaking when updating existing annotations. However, I wasn’t able to reproduce...

Hi @wmakley, Thank you for submitting such a detailed bug report ! The stacktrace was extremely helpful and allowed us to quickly identify the precise cause of the issue. You...

At the moment, there’s no built-in way to identify which file is causing the crash. It’s likely related to a .yml file being parsed when using --nested-position. As a temporary...

Hi @drwl 👋 I’d like to take on this task and work on adding automatic route annotation after migration tasks Before I start, I just want to confirm one detail...

Got it, thanks @drwl! I'll go ahead and implement it as an opt-in feature (enabled via something like `:auto_annotate_after_migrate:` in `.annotaterb.yml`). Let me know if you have any other preferences...