Conversation
|
Thanks for the suggestions! It may take some time for me to review this. In the meantime, I want to say up front that some of these enhancements, like That said, I see how there is value to extending nextgen to support more styles of Rails apps beyond my own preferences. Do you have any ideas for how nextgen could accommodate plugins/extensions, or otherwise be customizable so that interested developers can add their own custom generators? |
|
To customize enhancement selections, actually it's about customizing I think we can add "style" argument for
|
Implemented. |
|
@zhandao thanks again for your suggestions. I'm still deciding which of your proposals to merge into nextgen. For now, I would like to incorporate your idea to turn on the I also like the idea of organizing the generators into groups. The number of generators is really long, and I think organizing them will make for a better experience. I'll look into incorporating your ideas on that. |
|
@mattbrictson I have no objections 😄 Additionally, I've just found out that solid_queue will be the default job backend for Rails 8 (rails/rails#50442), so the idea should perhaps be reconsidered after Rails 8 release. |
|
EDIT: Moved to new issue at #110 |
|
EDIT: Moved to #110 |
Hi @mattbrictson
I'm enjoying using
nextgenand have some ideas want to share with you, so I open this. 😄The changes:
cycle, enum, filter)basic, job_backend, workflows, checkers, code_snippets, gems, and they only appear after yes -> More detailed configurationThe adding:
solid_queueCurrent.userRefactoring:
I extracted the helper methods from
Commands::CreateintoCommands::Helpersto reduce the length of file.But this caused a big git changes, may take some of your time, so sorry.