A good example of Igniter failing silently is if you copy the Igniter command line install command from this tutorial there’s probably some kind of fancy rich text formatting happening or something and neither the example code nor the Phoenix install occur, but Igniter only exits silently, it doesn’t say anything about aborting or not
1 Like
…I feel like I’m missing something obvious. I can tell that when I delete the some of those characters and retype them that it works…I don’t know if this is something igniter has anything to say about though. I think, to igniter, it’s just not getting any CLI arguments, and mix igniter.new helpdesk is a valid command that has that effect. So it’s not actually failing, it’s just not seeing those subsequent args. What on earth is going on there 
Hmm…this is weird.
Given a simple alias:
defp aliases do
[
foo: [
fn x ->
IO.inspect(x)
:ok
end
]
]
end
that prints out its argv, if you do:
mix foo helpdesk \ --install ash,ash_postgres \ --with phx.new \ --extend postgres \ --example
it prints out:
["helpdesk", " --install", "ash,ash_postgres", " --with", "phx.new",
" --extend", "postgres", " --example"]
notice the extra spaces at the head of the flags. This feels like some strange behavior of \?
If I add some OptionParser code in that alias:
OptionParser.parse!(x, strict: [install: :string])
it does not work if it gets a flag with a leading space. So I’m pretty sure thats why it also doesn’t work in igniter.
@kamaroly I think you should update the instructions in your post to use newlines after the \ or just remove the \ as they are only used in our examples to separate a task over multiple lines.
@josevalim This could be fixed in OptionParser or Mix also? Like should OptionParser or Mix trim leading whitespace? Or just OptionParser be adjusted to ignore leading whitespace?
1 Like
Nice Catch!
I just updated the article as recommended by @zachdaniel. I didn’t test it, but from the look of things. It should work.
2 Likes
