Hey everyone! Saša Jurić on his talk called Clarity @ ElixirConf EU 2021, mentions a way of architecting your code that uses a function that he names normalize/2, but sadly, he says he doesn’t have time to share it. I want to implement this programming style, but I’m missing this key ingredient. D…

I’ve not used it myself, but the tarams library looks like it might handle your use case if you want to go with a library instead of a custom solution GitHub - bluzky/tarams: Cast and validate external data and request parameters for Elixir and Phoenix · GitHub

I believe this is what you’re looking for: https://medium.com/very-big-things/towards-maintainable-elixir-the-core-and-the-interface-c267f0da43#1572 From my understanding, he just extracted the previous version of register into the normalize function.

As mentioned in the article, the author is suggesting using Ecto’ schemaless changesets for this . I think the normalize function can be written in a pretty generic way.

Thank @vrcca & @stefanchrobot for your pointers. I was able to recreate this function. I’ll leave it here for anyone who may find this post later. If you see anyway I can improve this code, please let me know :wink: defmodule Timetask.Helpers.Normalizer do import Ecto.Changeset @doc """ Nor…

[image] stefanchrobot: As mentioned in the article, the author is suggesting using Ecto’ schemaless changesets for this . I think the normalize function can be written in a pretty generic way. Yes, on both accounts. I can’t share the code (it’s owned by the clients), but the basic take is som…

Just a few remarks if you don’t mind: Enum.reject(schema, fn {_, v} I’d go with something longer and less generic than k (key?) and v (value?). Maybe {field, schema}? Plus in this case I think it makes sense to use {_k, v} to explain the meaning of the first element. cond do is_tuple(v) -> {k, …

I wanted to reply on Twitter but I saw there is already a solution in here. I’d like to share my anyway :slight_smile: Since we need to traverse the schema many times, I normalize it first and then use list comprehensions like this: def parse(params, schema) do # First I want to have entire …

[image] stefanchrobot: I’d go with something longer and less generic than k (key?) and v (value?) Noted. Definitely it’s a little cryptic. [image] tomekowal: Since we need to traverse the schema many times, I normalize it first and then use list comprehensions Oh yeah, the code looks …

I’d change String.to_atom by String.to_existing_atom , since this data comes from untrusted source.

[image] vrcca: I’d change String.to_atom by String.to_existing_atom , since this data comes from untrusted source. Good catch. I dindn’t know about that function :upside_down_face:

I’d be intersted in how you handled the return value of the core, especially for errors. It might be easy if db schema and normalized schema are similar, but becomes tricky when that’s not the case.