This contains snippets not only for the phoenix *.ex files (controllers, views, etc.), but also for templates. Very handy if you don’t want to keep typing <%= for ... %> and the like
This allows you to quickly open the most recent migration in a phoenix app.
Must have Atom opened with the phoenix app at the root.
Related Threads
I originally created this because I didn’t want to hijack the Famous thread any more on specifics with atom configuration, but I wanted to continue the discussion.
I’m still new to Elixir (three months now), and here is what I have tried so far with Atom: language-elixir (obvious ;)) autocomplete-elixir atom-elixir
I haven’t tried the linter-elixir-credo yet, but when I do incorporate credo I think I’ll give it a go.
My primary goal is to get a solid intellisense experience (at a minimum) and I simply cannot get it going.
Here is a screenshot using autocomplete-elixir:
It does not pick up the functions, but it does pick up the module scopes. This is a common occurrence (and yes, it does already compile).
Lately with atom-elixir, I can’t even get the autocomplete to pop up.
I already have one issue filed at both atom-elixir and autocomplete-elixir (regarding different issues), but as I’ve already stated: each one is developed and maintained by a single person.
My intention here is not to turn this into a troubleshooting thread though (although that would be fine by me if we could resolve it). But if it helps others get their stack up and going, I’m all for it.
I really think that this is a key blocker for the language, which as I’ve already stated a number of times, is superlative.
Now instead of troubleshooting, let’s look a little meta here. Maybe this is an environment problem. This day and age, with high release-cycle (agile) methodologies, we’re looking at multiple concurrent versions possibly. Also, the execution environment is diverse as well…multiple OSs, each of those with multiple versions.
So, no matter what the particular issue with my setup is, the point is that to increase productivity, something as essential as the developing environment (IMO of course) needs to be maintained and cared for to attract a broader target audience. Right now, and in the past, Erlang is niche for gurus with a focus on availability and concurrency. Elixir, as far as I can tell, is placing a higher emphasis on approachability with a broader audience: Solid documentation (), especially solid getting started documentation, great community tools (active and robust elixir forum + slack for new users, mailing list + IRC for existing gurus), superlative user-facing support via the best GitHub issue tracking I’ve ever seen, and a well established syntax (albeit Ruby, which I did not come from that environment).
Ok, I’ve said my piece on that stuff enough I think. As for this particular problem (backing away from the meta), I will probably file an issue here in the near future and hope that it gets responded to at some point in time in the future.
Hah. I was looking into one of the other packages you mentioned, elixir-cmd, and at the bottom of its readme it has:
it is active when the project has a mix file in its root directory
At some point in the past, I started using Atom at the base directory of my repo and not the umbrella app. This has brought back the functions. I wonder if atom-elixir works now.
Indeed. But should a newcomer to the ecosystem have to have that kind of special knowledge? I only ask in reference to ease the onboarding process. It’s always obvious once you know the answer!
Hi all, I’ve made the first post a Wiki for you - anyone at Trust Level 1 or higher can add/edit info into it
@ibgib, as the wiki owner, please keep any eye on things (help prevent spammers adding links etc). If at any point you can no longer oversee it let us know and we can assign someone else to it - thanks
@OvermindDL1 I’ve played briefly with credo, but I’ve not used the atom plugin at all. Would you mind adding some setup for how you config & use this? (linter-elixir-credo)
I just use a standard .credo.exs file in my root project directory to configure it, have it part of my project, installed the atom addon, not a whole lot to it, it is just a plugin into the linter package.
I notice in that screenshot that you don’t have a mix file in the root of the atom window. I’ve found many packages require a mix file in the root in order to work.
), especially solid getting started documentation, great community tools (active and robust elixir forum + slack for new users, mailing list + IRC for existing gurus), superlative user-facing support via the best GitHub issue tracking I’ve ever seen, and a well established syntax (albeit Ruby, which I did not come from that environment).
