Merge pull request #84 from mauricerkelly/support-different-mix-envir…

…onments

Include mixEnv parameter and apply to environment

README.md

@@ -40,6 +40,8 @@ Plugin should work with default settings. If not:
 
 5.  `always use elixirc` option - leave it disabled, unless `mix compile` is too slow.
 
+6.  `mix env` option - Allows changing the Mix environment for lint runs. If using IEx at the same time as Atom this can be changed to allow IEx to pick up code changes.
+
 ## Usage
 
 If you open folder with mix project (`mix.exs` exists in project's root

lib/init.js

@@ -13,6 +13,7 @@ const elixirProjectPathCache = new Map();
 let elixircPath;
 let mixPath;
 let forceElixirc;
+let mixEnv;
 
 function regexp(string, flags) {
   return new RegExp(
@@ -243,6 +244,7 @@ const getOpts = async filePath => ({
   throwOnStdErr: false,
   stream: 'both',
   allowEmptyStderr: true,
+  env: { MIX_ENV: mixEnv },
 });
 
 const getDepsPa = async (filePath) => {
@@ -322,6 +324,11 @@ export default {
         forceElixirc = value;
       }),
     );
+    this.subscriptions.add(
+      atom.config.observe('linter-elixirc.mixEnv', (value) => {
+        mixEnv = value;
+      }),
+    );
   },
 
   deactivate() {

package.json

@@ -25,6 +25,12 @@
       "title": "Always use elixirc",
       "description": "Activating this will force the plugin to never use `mix compile` and always use `elixirc`.",
       "default": false
+    },
+    "mixEnv": {
+      "type": "string",
+      "title": "Mix environment to use for linting",
+      "description": "Setting the Mix environment can avoid collisions between linter compiles and IEx sessions.",
+      "default": "dev"
     }
   },
   "providedServices": {