arc VS redux-form

def create(conn, %{"product" => product_params}) do changeset = Product.changeset(%Product{}, product_params) case Repo.insert(changeset) do {:ok, _product} -> conn |> put_flash(:info, "Product created successfully.") |> redirect(to: product_path(conn, :index)) {:error, changeset} -> render(conn, "new.html", changeset: changeset) endend params from log (I am using arc for handling image uploads in elixir code)

Alternative library that you might be interested: https://github.com/stavro/arc

GitHub Repository:

Handling form defaults

kyleboyle's proposal here simply doesn't work. When I call nextProps.handleSubmit from componentWillReceiveProps, I get this familiar error, Uncaught Error: You must either pass handleSubmit() an onSubmit function or pass onSubmit as a prop

[debug] Processing by SecretApp.ProductController.create/2 Parameters: %{"_csrf_token" => "Zl81JgdhIQ8GG2c+ei0WCQ9hTjI+AAAA0fwto+HMdQ7S7OCsLQ9Trg==", "_utf8" => "✓", "product" => %{"description" => "description_name", "image" => %Plug.Upload{content_type: "image/png", filename: "wallpaper-466648.png", path: "/tmp/plug-1460/multipart-754282-298907-1"}, "name" => "product_name", "price" => "100"}} Pipelines: [:browser] Api.ProductController handles requests from redux-from. Here is action, view and params, which are processed by this action:

The confusion multiplies when it comes to using libraries like react-redux-form or redux-form. I just want to simply have a model or something for name, surname email and password, but I feel that these libraries are over-engineered as soon as they start having their own reducer like:

I am trying to add a second submit button to a redux-form.

redux-form is a very compelling library for providing redux bindings for forms in a react application, which should be super-convenient. Unfortunately, using the library's own examples, I'm failing to actually bind anything, which is super in-convenient.