modeset / phoenix_simple_form

Easier form handling for the phoenix framework

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Phoenix Simple Form

Easy form handling for phoenix. Write <%= input f, :name %> and get wrappers with labels and error messages. Infers the type, comes with styles for bootstrap.

Hex.pm Version

Why

Usually you're styling your form the same across your app. Generators are okay but if you're writing the same code over and over again. But the better solution is to find a good abstraction. Simple form for phoenix does exactly that.

Installation

The package can be installed as:

  1. Add phoenix_simple_form to your list of dependencies in mix.exs:

    def deps do [{:phoenix_simple_form, "~> 0.0.2"}] end

  2. Ensure phoenix_simple_form is started before your application:

    def application do [applications: [:phoenix_simple_form]] end

  3. Run

    mix deps.get

Customization

You can customize styles and inferrers.

Styles

The default style for phoenix_simple_form is bootstrap4. (Feel free to contribute styles other css frameworks)

If you want to customize the style, add the following setting to your config.exs:

config :phoenix_simple_form,
  style: YourProject.YourStyle

Copy this file into your project. Rename the module name accordingly to your config setting.

To add a new style, just create a new input function.

def input(:custom_checkbox, f, name, opts) do
  content_tag :div, wrapper_html(opts, %{class: "checkbox"}) do
    [
      label(f, name, class: "checkbox") do
        [
        checkbox(f, name, input_html(opts, %{})), label_translation(f, name)]
      end,
      error_tag(f, name)
    ]
  end
end

You can use this by passing the as: option to an input field. E.g. <%= input f, :admin, as: :custom_checkbox %>.

If want to use this type every time a field is named admin or ends with _count or whatever, you can extend the type inferrer. See the next section for more information.

Type Inferrers

Inferrers try to infer the right input type for the available data. The default order is:

  1. Is the type is set explicitly with as:, use this type.

  2. If not, try to infer the type from the parameters. E.g. if the options list contains collection:, the type is automatically set to select field.

  3. If nothing else matches, read the model type from the database. Then e.g. :integer is mapped to a number input. :boolean is mapped to a checkbox.

If you want to customize the inferrer, add the following setting to your config.exs:

config :phoenix_simple_form,
  inferrer: YourProject.YourInferrerModule

Copy this file into your project. Rename the module name accordingly to your config setting.

Acknowledgments

The project is heavily inspired by Simple Form for Rails.

Contribution

This project uses the C4.1 process for all code changes.

"Everyone, without distinction or discrimination, SHALL have an equal right to become a Contributor under the terms of this contract."

tl;dr

  1. Check for open issues or open a new issue to start a discussion around a problem.
  2. Issues SHALL be named as "Problem: description of the problem".
  3. Fork the phoenix_simple_form repository on GitHub to start making your changes
  4. If possible, write a test which shows that the problem was solved.
  5. Send a pull request.
  6. Pull requests SHALL be named as "Solution: description of your solution"
  7. Your pull request is merged and you are added to the list of contributors

License

MIT

About

Easier form handling for the phoenix framework

License:MIT License


Languages

Language:Elixir 100.0%