fireproofsocks

fireproofsocks

I understand that the @moduledoc text is what gets shown when you type in mix help your.task:

Is there a way to show that information manually? For example, if my task has some required arguments or options, it’s possible to show an error using something like Mix.shell().error("Invalid input.), but I think it would be nicer in some cases to print out the usage info (just like you might encounter when you misuse a linux utility on the command line).

Thanks!

Showing Posts 1 to 9

NobbZ

NobbZ

You can just IO.puts @moduledoc.

fireproofsocks

fireproofsocks OP

Digging around in the source code for Mix.Tasks.Help, I can see that functions for this are not easily exposed.. for some reason, I’m having trouble calling the functions in IO.ANSI.Docs, e.g.

warning: IO.ANSI.Docs.print_markdown/2 is undefined or private.

What’s going on there?

fireproofsocks

fireproofsocks OP

Yeah, that’s what I’m doing so far, but it would be nicer to take advantage of the formatting.

josevalim

josevalim

Creator of Elixir
Mix.Task.run("help", ["name.of.your.task"])
axelson

axelson

Scenic Core Team

Also do note that IO.ANSI.Docs is @moduledoc false which means it is an internal implementation detail of Elixir and you should not be calling it from your code.

https://github.com/elixir-lang/elixir/blob/da9b9014575c1930049235b0509657b2bde47319/lib/elixir/lib/io/ansi/docs.ex#L2

NobbZ

NobbZ

Not sure which sources you are digging, but at least on 1.10.2 I wasn’t able to find that function.

And as already has been said, the module is considered “private” and can change without notice.

fireproofsocks

fireproofsocks OP

I thought @moduledoc false only indicated that documentation pages would not be generated. I do that on my own quickie projects where documentation isn’t necessary. It does not prevent me from calling the public functions in the module, however, so I am genuinely confused as to why I can’t call those functions.

NobbZ

NobbZ

@moduledoc false and @doc false are conventions for internally used functions that need to be exposed because they are used through the project, but are also not part of the public interface of the library.

The reason why you can’t call the function, is because the source code you looked at does probably not match the elixir version you have installed.

This is the reason why the module is marked “internal”, this gives the core team the flexibility to change it as necessary without needing to think about backwards compatibility.

fireproofsocks

fireproofsocks OP

Yeah, I’m looking at the latest master branch of the Elixir source… that must be different than the 1.10.1 code that I am actually running…

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews