kohkimakimoto / atom-atomenv Goto Github PK

It would be great to push environment variables per project, using an env file within the Atom dir. E.g.:

{
    "atom-atomenv" : {
        "env": {
            "FOO": "bar"
        }
    },
    "my-project": {
        "env": {
            "FOO": "bar"
        }
    }
}

To set variables for all projects, you can use the * like Atom does for the config file, e.g.:

{
    "*": {
        "env": {
            "FOO": "bar"
        }
    },
    "atom-atomenv" : {
        "env": {
            "FOO": "bar"
        }
    }
}

Having a .env file is a very frequent and conventional method to have env vars set within a project.

Format is trivial (see link above):

FOO=bar
BAZ=qux

I've tried creating an .atomenv.cson file in my .atom directory and did the auto-load but when I try to use the variables in the .atomenv.cson file they don't render except as plain text and the file is in the same directory as the atom config.cson

.atomenv.cson

env:
  beautifyAnalyticsUserId: "..."
  exceptionReportingUserId: "..."

config.cson

"*":
  "atom-beautify":
    general:
      _analyticsUserId: "${atom.config.get('atomenv.env.beautifyAnalyticsUserId')}"

This part though when loading it shows it loaded Atomenv in the console but when I run atom.config.get() I do not see atomenv in the array

I've even tried

"*":
  "atom-beautify":
    general:
      _analyticsUserId: "${env.beautifyAnalyticsUserId}"

Is it not meant to run as global environment or am I missing something?

Is possible use atomenv and GOPATH definition with go-plus package? I setup .atomenv.json in my project directory, but when I open new project the go-plus pkg still have old (default) GOPATH value... 🤔