Mathias Polligkeit

I just made a fresh install of nix, nix-darwin and home manager. I had this in my config: ```nix { imports = [ ]; environment = { darwinConfig = "$HOME/.config/nixpkgs/darwin/configuration.nix";...

Thanks for opening the issue. We have custom fields, which should allow you to model this: https://hexdocs.pm/flop/Flop.Schema.html#module-custom-fields

> But now that I've typed all this up I realized that it's just so much conceptually simpler if I drop all the two-date-inputs-with-one-flop-field shenanigans and just use two separate...

Hi @mustela, I'm not working on this currently, but here's a related discussion: https://github.com/woylie/flop/discussions/415.

Replacing `inputs_for` with the component version is not possible, since the `Phoenix.HTML.FormData` implementation for `Flop.Meta` relies on the `fields` option being passed, but `Phoenix.Component.inputs_for/1` doesn't allow to pass additional options...

It would probably make sense to add an `attr :opts, :list, default: []` to `Phoenix.Component.inputs_for/1`. The documentation for [`Phoenix.HTML.FormData.to_form/2`](https://hexdocs.pm/phoenix_html/Phoenix.HTML.FormData.html#to_form/2) states: > The options have their meaning defined by the underlying...

Yes, some flop_phoenix tests start failing when I switch to the `inputs_for` component because the IDs aren't as expected. I haven't found the issue yet.

@jelkand That is very helpful, thanks for looking into this! I didn't have a closer look yet, but I'd like to understand better what the purpose of the `_persistent_id`, and...

> This change is essential to be able to use Bootstrap5 CSS with Flop.Phoenix (bootstrap is very particular with how elements must nest inside each other. Probably needs some tests...

stale