If I have a full understanding, you say this because we don't want to really know what the args of `init/2` are, because `gen_server` needs `init/1` at every case, and we only want to check that if...
> > The only test that is not working now is the one with the `init([])` because its attribute type is `nil`. I don't know how I will solve this, it may need some extra magic. Or is it a bug in `ka...
I still think it would be better to filter out more functions here…
```suggestion
IsFunction = fun(Node) -> ktn_code:type(Node) == function andalso ktn_code:attr(name, Node) == in...
> The only test that is not working now is the one with the `init([])` because its attribute type is `nil`. I don't know how I will solve this, it may need some extra magic. Or is it a bug in `kata...
The only test that is not working now is the one with the `init([])` because its attribute type is `nil`. I don't know how I will solve this, it may need some extra magic. Or is it a bug in `katana...
> > Yes! I like making more and more tests to feel that my code is 100% good.
>
> HA! I just saw that you were matching against a single `[BehaviourNode]` in your code… and I wondered "what woul...
> Yes! I like making more and more tests to feel that my code is 100% good.
HA! I just saw that you were matching against a single `[BehaviourNode]` in your code… and I wondered "what would happ...
> One more test (or maybe two, if you want a fail and a pass), @bormilan:
>
> * A module that implements `gen_server` AND another behaviour…
>
> ```erlang
> -module(fail…).
>
> -behaviour...
One more test (or maybe two, if you want a fail and a pass), @bormilan:
* A module that implements `gen_server` AND another behaviour…
```erlang
-module(fail…).
-behaviour(gen_server).
-...
One more test (or maybe two, if you want a fail and a pass), @bormilan:
* A module that implements `gen_server` AND another behaviour…
```erlang
-module(fail…).
-behaviour(gen_server).
-...
One more test (or maybe, two), @bormilan:
* A module that implements `gen_server` AND another behaviour…
```erlang
-module(fail…).
-behaviour(gen_server).
-behaviour(another_behaviour).
...
You can (probably… I had not tested it) simplify this multi-loop algorithm on a single list comprehension…
```suggestion
case is_rule_behaviour(Root, RuleConfig) of
true ->
...
Renaming suggestion: `is_relevant_behaviour` or `is_important_behaviour` or `is_known_behaviour`.
`is_rule_behaviour`, to me, sounds like if it's looking for `-behaviour(rule).`