Automatically create output folders

[lorenz]

This is an implementation of google/jsonnet#195 for the Go version since the concerns mentioned in that issue are of no concern in a Go application. It's just a very quick fix done for my own needs, feel free to reject in case you don't want any divergence from the C++ implementation.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

[coveralls]

Coverage increased (+3.1%) to 75.14% when pulling 29b520a on lorenz:master into 9a9954a on google:master.

[lorenz]

Signed the CLA

[googlebot]

CLAs look good, thanks!

[sparkprime]

This is great but can you put it in a flag that's off by default and also make it do it in the single file case?

[lorenz]

Sure

[lorenz]

Made it into an option and added single file support

[lorenz]

The failed tests are in the cpp-jsonnet repo, how should this be synchronized? If the PR there goes in before this one, the build is broken and the other way round too.

[sbarzowski]

Oh, we're comparing help output directly. Well this is our test mechanism's fault, sorry about that. It's not very important how we go around it, as long as we update both in the timespan of less than few hours. Pehaps later we can move implementation-specific output to implementation repo (it should be just a few lines of changes in the scripts).

[sparkprime]

I believe it should be possible to update cpp-jsonnet but not go-jsonnet, and then go-jsonnet will not take that version of cpp-jsonnet until it is updated, so you can do that update at the same time as introducing the change.

[lorenz]

Update seems to have broken another assertion (non cmd-related), not sure about that

[sbarzowski]

I don't think it has anything to do with this change. It's happened just because of the submodule update. I'll investigate later today.

[sbarzowski]

As I thought, it's just the matter of updating stdlib to match C++ updates (there was a bugfix related to escaping there). If you add this commit to the pull request the tests should run fine sbarzowski@baff839

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

[lorenz]

Looks good now

[sbarzowski]

Yes, I'm officially ok with my commit being merged here.

[sparkprime]

Thanks

[alem0lars]

Is this feature released?

[sbarzowski]

Yes