GAE prod and dev support for datastore

Fixes #104.
I called Object.defineProperty magical.

I call other languages that implement getter setter functions on fields
without being explicit magical similarly. Instruction time should not be
able to alter a "field"s value if object state is not modified. So given
the choice, I'd minify the use of non-explicit getters :)

Anyways, that's too much of language design discussion for a minimal
feature.

On Mon, Sep 8, 2014 at 4:54 PM, Stephen Sawchuk <notifications@github.com>
wrote:

> In lib/common/gae.js:
>
> > + * Unless required by applicable law or agreed to in writing, software
> > + * distributed under the License is distributed on an "AS IS" BASIS,
> > + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
> > + * See the License for the specific language governing permissions and
> > + * limitations under the License.
> > + */
> > +
> > +/**
> > + * @private
> > + */
> > +
> > +'use strict';
> > +
> > +var gae = {};
> > +
> > +gae.info = function() {
>
> In other words, what you have currently?
>
> I wouldn't call gae.id returning the gae id env variable magical. Unless
> you mean the implementation with Obj.defineProperty, which also isn't
> really doing anything magical.
>
> If we're shaping code for the benefit of tests, we might as well have the
> benefit of it working logically in non-test environments.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/GoogleCloudPlatform/gcloud-node/pull/154/files#r17275053>
> .
>



-- 
Burcu Dogan