Reference environment variables

[brettlangdon]

Got the idea from HOCON #9

I am thinking the syntax would look like:

debug = ${APP_DEBUG};

And have the ability to set a default value if the environment variable does not exist:

debug = ${APP_DEBUG ? "true"};

I haven't decided if the values should always be strings, or if they should be coerced where applicable. e.g. should the string value of true be converted into a boolean, same for null, false, or integers.

[brettlangdon]

As per #19, I ended up going with path = $PATH, however, haven't decided if I want to merge yet, if I actually want this feature or not.

[jeevatkm]

While looking for config file format, I have reached here. Can you please make this environment variable substitution possible? I would like to use forge for my project 👍 Thanks for making this library.

BTW, what do you call forge config syntax?

[brettlangdon]

@jeevatkm unfortunately we have decided previously not to support this feature and unfortunately there hasn't been many requests for supporting it in the last year.

If this feature is stopping you from otherwise using forge, I do have the code supporting environment variables on a branch (see this closed PR #19) and I would not at all be upset if you forked and used that code for your project.

I had never really thought of naming the syntax... I guess.. "forge syntax"? As mentioned in a previous issue by another user (see #9), the syntax is very similar to that of HOCON, although not 100% compatible. I didn't necessarily model it after an existing syntax.

[jeevatkm]

@brettlangdon Thank you for the direction. For now I will fork and apply #19 PR on that.

Yeah you're correct, forge is similar to HOCON syntax. For I will document it as forge syntax once you decide on name let me know.

Sorry for dragging, is there any plan on resolving URL on include token?

[brettlangdon]

Sounds good.

No plans to resolve URLs for includes.
On Jun 29, 2016 1:09 AM, "Jeevanandam M." notifications@github.com wrote:

@brettlangdon https://github.com/brettlangdon Thank you for the
direction. For now I will fork and apply #19
#19 PR on that.

Yeah you're correct, forge is similar to HOCON syntax. For I will document
it as forge syntax once you decide on name let me know.

Sorry for dragging, is there any plan on resolving URL on include token
https://github.com/brettlangdon/forge/blob/master/parser.go#L249?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#13 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABQloXb0O6G72C_G_y3fjB063VzOfjvuks5qQf3vgaJpZM4FRa-n
.

[jeevatkm]

Thanks!