lawik
I have a library that wants to find all modules for a given behaviour. I found some description that showed how to do this off of :code.all_loaded() which was neat. Then I moved the library out of the application it was living in because it really isn’t supposed to be an application on its own. And things started breaking intermittently during testing.
So that’s when I found out about Elixir doing lazy loading of modules through this thread. But the build_embedded stuff only really seems to apply to an application.
Should I just use another approach for this? I want to find all modules that are widgets. I was doing this at runtime, building the list when it was first requested and persisting it to the Application environment. I don’t really care if the initial list is made at compile time or runtime. Ideally it should also be able to register new Widgets if they are loaded at runtime or come from outside the library.
Is there a common pattern recommended here that I’m just not familiar with? I realize this is state but the library is mostly pure functions so avoiding needing to start a supervision tree for the lib would be more elegant.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Phoenix, LiveView, multimedia pipelines, distributed systems. 400 engineers, Elixir since 2017. Available for hire.
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
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
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.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
I’ve tried to do similar things in the past and tbh the best/most flexible thing you can do it let your users provide a list somewhere. All other options have downsides like needing global state or your case of a certain embedded mode, …
christhekeele
I messed around with metaprogramming using module compilation hooks to achieve a way to track what modules
useother modules a few years ago. It could be applied here to track behavior usage.You have to own the module being used, and clients have to use
useinstead of@behaviour. But it will let the library track all modules at compile time, across other libraries and umbrella apps.Not that this probably isn’t a great idea, one of the whole points of having behaviours is to define an interface that others can call dynamically with arbitrary modules.
Also note I haven’t tried this out for years, so may not work verbatim on recent elixirs.
lawik
Thanks, I’ve gone for an Agent storing the list for now. So that needs to be loaded at startup. It’ll do.