You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using rails-erd since the start of a project and now I got a pretty large data structure, it became hard to read a single erd graph, so I tried to split it into meaningful parts.
For that I found the config_file option really useful, I ended up creating a custom rake task that calls erd with all my different config files. The pain point is that I now have my own rake task to generate splited erds, but the default one is still for the whole DB.
I managed the auto-call when migration by overriding "self.update_model" method in ERDGraph::Migration from lib/tasks/auto_generate_diagram.rake
I also cleared "erd" task in my Rakefile to redefine it with my own erd-generating rake task. So when I type "rake erd" I got the expected output.
But at least when I run "bundle exec erd" it is still the gem default task called.
Is there an easiest way to obtain the same result ? Or a way to change default behavior to end with same behavior from all entry points ? Maybe it could be a new feature ?
The text was updated successfully, but these errors were encountered:
Hey there,
I'm using rails-erd since the start of a project and now I got a pretty large data structure, it became hard to read a single erd graph, so I tried to split it into meaningful parts.
For that I found the config_file option really useful, I ended up creating a custom rake task that calls erd with all my different config files. The pain point is that I now have my own rake task to generate splited erds, but the default one is still for the whole DB.
I managed the auto-call when migration by overriding "self.update_model" method in ERDGraph::Migration from lib/tasks/auto_generate_diagram.rake
I also cleared "erd" task in my Rakefile to redefine it with my own erd-generating rake task. So when I type "rake erd" I got the expected output.
But at least when I run "bundle exec erd" it is still the gem default task called.
Is there an easiest way to obtain the same result ? Or a way to change default behavior to end with same behavior from all entry points ? Maybe it could be a new feature ?
The text was updated successfully, but these errors were encountered: