Credo check for encouraging pattern matching by struct in the parameters

Hi folks!

With the new release of Elixir 1.18, I would like to enforce pattern-matching by struct in our projects to take advantage of the type inference. To do so, I’m working on a Credo check and I would like feedback.

The rule will do the following:

:stop_sign: Pattern-matching by an atom key of a map:

# not preferred
def get_role(%{role: role}) do # if the map keys are atoms it should be a Struct.
  role
end

:white_check_mark: Pattern-matching by struct

# preferred
def get_role(%User{role: role}) do
  role
end
# preferred
def get_role(user = %User{}) do
  user.role
end

I’ve found that there are cases where there are maps with atom keys and they don’t have to be structs, like in the props of the LiveView Components, or the Phoenix Controllers, but I think it is worth having this check and disable it for those cases, or cheat the rule moving the pattern matching inside the body of the function like for this case:

def update(%{param_1: param_1, param_2: param_2}, socket) do
  ...
end

doing:

def update(params, socket) do
  %{param_1: param_1, param_2: param_2} = params
  ...
end

Do you think it would make sense? Would you find it useful enough to add it to Credo?

Hey, welcome to the forum!

It can be contentious but I often destructure params inside the function body, preferring to only match what’s necessary in the function head (within reason). It’s even mention in the anti-pattern guide. That is just to say it’s hard to handle that case as it’s often legit. In any event, I think there needs to be some level of trust there!

Otherwise, it may be overkill but if there is a bare map you could have the rule require adding a guard with is_non_struct_map/1.