Brujo Benavides

Cowboy to 2.4.0 in particular, but the others as well.

We can add a `binding_id` property to the trail options for the handlers and use that instead of assuming the parameter is always called `:id`. That property might default to...

…instead of processing them all as binaries.

Once #70 is done, add walls into greedy's avoid_collision function

Out of Order Updates

1

Server needs to ignore out of order client updates. It's currently crashing.

Now when you use a numeric id there it traverses the whole list of games to find the right one.

Not being able to express `ignore => [atom()]`, in the options, is hindering

1

@paulo-ferraz-oliveira said… > On a more serious note I find that not being able to express `ignore => [atom()]`, in the options, is hindering. I had to do "`src/module.erl`" (didn't...

@format collides with edoc

26

As detected by @awalterschulze on WhatsApp/erlfmt#277, we probably need a new tag format.

Basically, revert this change: https://github.com/AdRoll/rebar3_format/pull/300#discussion_r847337945

Using a macro as an attribute name crashes the formatter

1

This is the nasty case… ```erlang -define(attrib, some_attrib). -?attrib([foo2/2]). ``` Which produces an error: ```erlang {function_clause, [{erl_recomment,leaf_node_value, [{tree,10,10,macro, {attr,10,[],none}, [],[], [{list,10,10, [{leaf,10,10,[],[], {tree,atom,{attr,10,[],none},attrib}}]}]}], [{file,"erl_recomment.erl"},{line,711}]}, {erl_recomment,check_file_attr_1,2, [{file,"erl_recomment.erl"},{line,282}]}, {erl_recomment,filter_forms,3,[{file,"erl_recomment.erl"},{line,229}]}, {erl_recomment,filter_forms,3,[{file,"erl_recomment.erl"},{line,253}]}, {erl_recomment,recomment_forms,3,[{file,"erl_recomment.erl"},{line,136}]}, {rebar3_formatter,format,4,...