Should it be allowed to generate live/html/json/... without attributes?

[agonzalezro]

Environment

• Elixir version (elixir -v): 1.16.1
• Phoenix version (mix deps): 1.17.1
• Operating system: Sonoma

Actual behavior

After a generation without attributes:

mix phx.gen.live Todos Item items

and adding the routes I get an error on the view:

key :col not found in: %{
  __changed__: nil,
  __given__: %{
    __changed__: nil,
    action: [
      %{
        __slot__: :action,
        inner_block: #Function<5.76604854/2 in FooWeb.TodoLive.Index.render/1>
      },
      %{
        __slot__: :action,
        inner_block: #Function<6.76604854/2 in FooWeb.TodoLive.Index.render/1>
      }
    ],
    id: "todos",
    ...

Expected behavior

The error itself make sense, I wonder if there are cases when it's useful to use the generator without providing attributes or it's just an error.

Please, let me know if it's an error and I can try to provide a patch.

[josevalim]

If there are no columns, maybe the generator should then use the id column as the initial column?

[agonzalezro]

I am trying to understand if there is a real use case behind a generation without any attribute.

Fixing the table in the index is easy as you said by just showing the ID column. However, there are some other small changes that need to be done to make this work and I don't know if they are worthy. For example, in the FormComponent's save event it will be needed to support an empty object.

I am happy to do those changes to the generator if it helps, but I am leaning more toward the option of just fail if the phx.gen.live or others are being called without attributes.

[angyan]

I got the same error when I ran the phx.gen.html with --no-context and --no-schema. The use case then would be when someone generates a context with a schema first and then runs the phx.gen.html to generate the HTML scaffolding.