All Versions
39
Latest Version
Avg Release Cycle
18 days
Latest Release
982 days ago

Changelog History
Page 1

  • v0.6.7

    June 16, 2017
    • 🛠 Fixed #17 - when there was more than 9 items in collections, they were ordered 1, 10, 11 ..., 2, 20, 21..., 3...

  • v0.6.6

    May 25, 2017
    • 🛠 Fixed #15 - issue in collections, when id of struct was "" instead of nil
    • 🔄 Changed Validator module to be compatible with Formex.Ecto 0.2

  • v0.6.5

    April 01, 2017
    • 🛠 Fixed using multi_select with array field when value of field is nil

  • v0.6.4

    March 08, 2017
    • 🔄 Changed argument of custom_value callback

  • v0.6.3

    March 07, 2017
    • âž• Added a custom_value option in fields

  • v0.6.2

    February 21, 2017
    • âž• Added another way to define the translate_error function, to fix usage with Distillery. Details are in Formex.Validator docs.
    • âž• Added a default translate_error implementation, so you don't need to set it in config.ex, when you don't want to translate error messages.

  • v0.6.1

    February 16, 2017
    • 🛠 Fixed file uploads in collections

  • v0.6.0

    December 26, 2017

    • 🔄 Changed behaviour when user sends no value for field.

      Example

      You have a form with first_name and last_name fields, and user manually removes in browser the first_name field.

      What happens after form submit:

      • Prior to formex 0.6.0, the first_name value will be unchanged.
      • Since 0.6.0, the first_name value will be "".

      This new behaviour is the same as in the Symfony form library. It was necessary to change, because browser sends no value in multiple_select if there is nothing selected, or even there may be no value in normal select when we using Ajax Bootstrap Select plugin and was nothing selected.

    • 🛠 Fixed deselecting all options in multiple select jakub-zawislak/formex_ecto#2

  • v0.5.10

    December 13, 2017
    • 🔄 Changed behaviour of select validation. When user tried to provide an invalid select value (that wasn't in list of available options), an elixir error was raised. Since now user will see message "invalid value" attached to field, instead of server error. This message can be translated via gettext.

  • v0.5.9

    December 05, 2017