sarat1669
I have a module which defines a behavior
defmodule Light.Trigger do
@callback initialize(%{}) :: {:ok, any()}
defmacro __using__(_) do
quote do
use GenServer
@behaviour Light.Trigger
...
end
end
And I am using it like
defmodule Light.Test do
use Light.Trigger
@impl true
def initialize(state) do
{:ok, state}
end
@impl true
def handle_info(:test, state) do
...
{:noreply, state}
end
end
This happens
iex> Light.Test.module_info[:attributes][:behaviour]
[GenServer]
But it should be
iex> Light.Test.module_info[:attributes][:behaviour]
[GenServer, Trigger]
right?
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sarat1669
On further inspection:
John-Goff
You can use Keyword — Elixir v1.20.2 to get the list that you want.
hauleth
1.Use more idiomatic
mod.module_info(:attributes).2. It will mention only behaviours set via module attribute (you do not need to set that to implement behaviour). So there is no “100% correct” solution to list all implemented behaviours.
sarat1669
Is there a case where, the
behaviourin module_info is a returned as a list with multiple behaviours? If not, should this be treated as a bug?eksperimental
It should not really matter whether it accepts a list or not (it does not FYI).
This is the way attributes work with accumulate
true.bit4bit
see model_info i think it’s work as expected: