Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] API for yam.set() #7

Open
runspired opened this issue Dec 25, 2014 · 1 comment
Open

[Feature] API for yam.set() #7

runspired opened this issue Dec 25, 2014 · 1 comment

Comments

@runspired
Copy link

It looks as though yam used to have the ability to write as well as to read variables. 6fce91e

I'm working on a PR for ember-cli-cordova that will require storing a configuration setting in .ember-cli when the main blueprint generation is done.

It would add both a namespace (cordova) and a setting (multiEnv):

   cordova : {
       multiEnv : true
   }

Is .set() a feature that we could bring back? It does obviously make yam a little more clunky to avoid stripping comments, but it would be great to have a lib for writing to config files from ember-addons.

@selvagsz
Copy link

👍 for this feature. Curious to know the reason behind the removal of .set ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants