Wígny Almeida

These are really good reasons we need to solve first! Since your comment, I've been trying to figure out how we can solve these points, but given my lack of...

> the problem happens trying to use this scalar for mutations, one of the sub type data we need to send is a list I'm facing the same requirements right...

> I want to distribute the remainder as evenly as possible amongst the requested # of parts. Recursion could be handy here, right? ```elixir def split(_money, 0) do [] end...

Hey @SteffenDE, could you say if we are expected to have a similar behaviour provided by the now deprecated `phx-feeback-group` when using the new `used_input?/1` helper in those "composite inputs"?...

Hey @SteffenDE, thanks for the suggestion. I think this small helper can give us better control of whether to show error messages. > We should probably make this more convenient....

Rewriting the code to the following avoids the warning, but I'm unsure if that is the right solution. ```elixir defmodule Test do for n

Yes, it worked great, thanks! The only case the change didn't cover in our codebase was ```elixir unquote(context).unquote(:"get_#{type}_by")(id: id) ``` which I believe could have been written as this instead...

> store in the application the "documentation_url" I believe it would be great to have it alongside `source_url` and `homepage_url` so maybe projects like [`ElixirLS`](https://github.com/elixir-lsp/elixir-ls) could also make use of...

Uhmm, so it means that when I call `fill_in(form, "Name", with: "John")`, it will never alone change the input value in a way that changes the form payload? I'm wrong...