You sir, are awesome!
dwark
al2o3cr
Followup: if you use the :overspecs flag in your Dialyxir config, you get a much more intelligible error message (among a BUNCH of messages):
________________________________________________________________________________
lib/teiserver/lobby/libs/lobby_restrictions.ex:130:missing_range
The type specification is missing types returned by function.
Function:
Teiserver.Lobby.LobbyRestrictions.check_rank_to_play/2
Type specification return types:
:ok | {:error, binary()}
Missing from spec:
{:error, [<<_::64, _::size(8)>>, ...]}
________________________________________________________________________________
lib/teiserver/lobby/libs/lobby_restrictions.ex:163:missing_range
The type specification is missing types returned by function.
Function:
Teiserver.Lobby.LobbyRestrictions.check_rating_to_play/2
Type specification return types:
:ok | {:error, binary()}
Missing from spec:
{:error, [<<_::64, _::size(8)>>, ...]}
Unfortunately, you also get a TON of these:
________________________________________________________________________________
lib/teiserver_web/controllers/api/hailstorm_controller.ex:205:contract_subtype
Type specification is a subtype of the success typing.
Function:
Teiserver.API.HailstormAuth.authorize/3
Type specification:
@spec authorize(Atom.t(), Plug.Conn.t(), Map.t()) :: Boolean.t()
Success typing:
@spec authorize(_, _, _) :: any()
Somewhat annoying that those two checks are only available together, as the former seems like a much stronger “there may be a bug” signal than the latter. 
0