I am currently enrolled in the Pragmatic Studio Elixir & OTP course and have just completed the section on module attributes. I have the following code: defmodule Servy.Handler do @moduledoc "Handles HTTP requests" @pages_path Path.expand("../../pages", __DIR__) @doc "Transforms the request…

Someone else can probably give you a more detailed answer but I think the problem here is that you are running a script (.exs file). Scripts as I understand are only compiled into memory so there’s no beam file on disk to read the docs from.

Actually, it’s an .ex file (executable). [script extension]

To be clear, .ex is not an executable, it’s just an elixir file. .beam are the bytecode files. In short, modules in iex are loaded into memory so not compiled with docs. I’m not sure if there is a way to do so or not. If you have a mix project, though, and load it in with iex -S mix then you’ll …

How are you compiling it? If you are doing c("handler.ex") in iex it still defaults to in-memory regardless of whether it’s a .exs file.

[image] sodapopcan: In short, modules in iex are loaded into memory so not compiled with docs. I’m not sure if there is a way to do so or not. Looks like c/2 accepts a path as the second argument .

Oh neat! They’ve thought of everything :sweat_smile:

Iex help command not working

Questions & Help Questions

Ookma-Kyi May 23, 2025, 6:01pm 3

Actually, it’s an .ex file (executable).