lucky gen.resource.browser support skip model/migrations, or a new task for this.

[zw963]

Basically, this same as following rails scaffold_controller task.

rails g scaffold_controller --help
escription:
    Generates a scaffolded controller, its seven RESTful actions and related
    views. Pass the model name, either CamelCased or under_scored. The
    controller name is retrieved as a pluralized version of the model name.

    To create a controller within a module, specify the model name as a
    path like 'parent_module/controller_name'.

    This generates a controller class in app/controllers and invokes helper,
    template engine and test framework generators.

Example:
    `bin/rails generate scaffold_controller CreditCard`

    Credit card controller with URLs like /credit_cards.
        Controller: app/controllers/credit_cards_controller.rb
        Test:       test/controllers/credit_cards_controller_test.rb
        Views:      app/views/credit_cards/index.html.erb [...]
        Helper:     app/helpers/credit_cards_helper.rb

Thanks

[jwoertink]

lucky gen.action.api or lucky gen.action.browser. lucky -h to see more

▸ gen.action.api         Generate a new api action
▸ gen.action.browser     Generate a new browser action
▸ gen.component          Generate a new HTML component
▸ gen.migration          Generate a new migration
▸ gen.model              Generate a model, query, and operations (save and delete)
▸ gen.page               Generate a new HTML page
▸ gen.resource.browser   Generate a resource (model, operation, query, actions, and pages)

[zw963]

Both of above tasks(except resource), only create one file.

the usecase for rails g scaffold_controller is, create all CRUD action + views, in one shoot.

e.g. following was the created file when run rails g scaffold_controller posts title:string,

      create  app/controllers/posts_controller.rb
      invoke  erb
      create    app/views/posts
      create    app/views/posts/index.html.erb
      create    app/views/posts/edit.html.erb
      create    app/views/posts/show.html.erb
      create    app/views/posts/new.html.erb
      create    app/views/posts/_form.html.erb
      create    app/views/posts/_post.html.erb
      invoke  resource_route
       route    resources :posts
      invoke  test_unit
      create    test/controllers/posts_controller_test.rb
      create    test/system/posts_test.rb
      invoke  helper
      create    app/helpers/posts_helper.rb
      invoke    test_unit
      invoke  jbuilder
      create    app/views/posts/index.json.jbuilder
      create    app/views/posts/show.json.jbuilder
      create    app/views/posts/_post.json.jbuilder

So, it should be a subset of lucky gen.resource.browser.
when try to run lucky gen.resource.browser Manufactory name:String, will raise following error if the model and migration already exists.

nhandled exception:   Migration name must be unique

  Migration name: create_manufactories.cr already exists as: 20220730132541_create_manufactories.cr. (Exception)
  from lib/avram/src/avram/tasks/gen/migration.cr:74:9 in 'ensure_unique'
  from lib/avram/src/avram/tasks/gen/migration.cr:25:5 in 'generate'
  from lib/avram/src/lucky/tasks/gen/mixins/migration_with_columns.cr:5:5 in 'create_migration'
  from lib/avram/src/lucky/tasks/gen/resource/browser.cr:45:5 in 'generate_resource'
  from lib/avram/src/lucky/tasks/gen/resource/browser.cr:36:5 in 'call'
  from lib/avram/src/lucky/tasks/gen/resource/browser.cr:8:1 in 'print_help_or_call'
  from lib/lucky_task/src/lucky_task/runner.cr:25:9 in 'run'
  from tasks.cr:25:1 in '__crystal_main'
  from /home/zw963/Crystal/share/crystal/src/crystal/main.cr:115:5 in 'main_user_code'
  from /home/zw963/Crystal/share/crystal/src/crystal/main.cr:101:7 in 'main'
  from /home/zw963/Crystal/share/crystal/src/crystal/main.cr:127:3 in 'main'
  from /usr/lib/libc.so.6 in '??'
  from /usr/lib/libc.so.6 in '__libc_start_main'
  from tmp/tasks_binary in '_start'
  from ???

So, i consider if we can add a option to skip model + migration, from my point of view,
this is a quite common request, i create db/model at first, but, only create CRUD scaffold when need.

[jwoertink]

This seems kind of confusing to me. So you would run lucky gen.browser.resource Post --without-model and get

src/actions/posts/index.cr
src/actions/posts/show.cr
src/actions/posts/new.cr
src/actions/posts/create.cr
src/actions/posts/edit.cr
src/actions/posts/update.cr
src/actions/posts/delete.cr
src/pages/posts/index_page.cr
src/pages/posts/show_page.cr
src/pages/posts/new_page.cr
src/pages/posts/edit_page.cr

But that's it? If you skip the model, you wouldn't get migrations, queries, operations, serializers, or the model. But now you'd have to go back and fill in all of the code for all of these which would lead to a lot more typing, and possibly missing something which might cause issues.

If there's no model, we can't prefill the the actions or pages with model related code since that would break Lucky convention. And we can't assume you created the model before hand since there would be no way to detect it because the generators are precompiled.

[zw963]

Alright, this new option will assume the user know what he want, this is precondition, not all model need the RESTFul CRUD in advance, this just a way as a supplement.

BTW: Do we consider add a new task which assemble the action with page, e.g. it is useful when create a action along with a same name page.

lucky gen.action.browser Admin::Companies::Edit
lucky gen.page Admin::Companies::EditPage

so, the above two file can be created at same time use only one command. (consider when run lucky command, always need wait several seconds to compile, this is more worthy)

[jwoertink]

I think that could be useful. Maybe lucky gen.action.browser Admin::Companies::Edit --with-page ? Or would we name this different?

[zw963]

--with-page LGTM.