add metadata update to example and fix builder user-settable fields

[aozarov]

No description provided.

[coveralls]

Coverage decreased (-0.12%) to 52.9% when pulling 6c59a54 on aozarov:master into 76776e3 on GoogleCloudPlatform:master.

[jboynes]

This PR is a combination of different changes. It would be clearer if these were separate requests with their own descriptions

[coveralls]

Coverage increased (+5.68%) to 58.71% when pulling 17ec594 on aozarov:master into 76776e3 on GoogleCloudPlatform:master.

[coveralls]

Coverage increased (+5.68%) to 58.71% when pulling 17ec594 on aozarov:master into 76776e3 on GoogleCloudPlatform:master.

[coveralls]

Coverage increased (+5.68%) to 58.71% when pulling 4b8bd32 on aozarov:master into 76776e3 on GoogleCloudPlatform:master.

[aozarov]

Changes were applied yesterday. Not sure if an explicit PTAL is expected.

[coveralls]

Coverage increased (+5.63%) to 58.66% when pulling 96b3ada on aozarov:master into 76776e3 on GoogleCloudPlatform:master.

[aozarov]

I played few hours o deal with git and gitHub branches to avoid having the last commit "Replace given null values with Apiary nulls and provide doesNotExists" be part of this push request but unfortunately did one mistake (forgot to switch to my local branch before applying the patch which I had ready) and realized it after I pushed. This is not a big change and I don't want to play with rolling it back, so I leave it as part of this push. Honestly the process which I am following (maybe there is a better one) is annoying as I have to find the state of the master before my push request and branch from it each time to avoid including its pending changes so a quicker turn-around would be appreciated.

[jboynes]

There's a lot of stuff that got added here - it will take me a little while to go through it.
The workflow I use, which I think is pretty typical git, it to have separate branches for separate features and then merge between them as needed. If there are dependent changes, then rebase off the parent branch after merging in the feedback.

[aozarov]

The issue for me was co-coordinating it with gitHub (and basically making
sure that the branch does not include what is already pending).
I didn't add much today and many of the previous changes are trivial such
making things final and overriding equals and hashCode.

Arie | Ozarov | ozarov@google.com | 415-624-6429

On Wed, May 13, 2015 at 5:01 PM, Jeremy Boynes notifications@github.com
wrote:

There's a lot of stuff that got added here - it will take me a little
while to go through it.
The workflow I use, which I think is pretty typical git, it to have
separate branches for separate features and then merge between them as
needed. If there are dependent changes, then rebase off the parent branch
after merging in the feedback.

—
Reply to this email directly or view it on GitHub
#58 (comment)
.

[coveralls]

Coverage increased (+5.63%) to 58.66% when pulling 0299172 on aozarov:master into 76776e3 on GoogleCloudPlatform:master.