Feedback requested for accessing property values

[googleapis]

Feedback requested for accessing property values

[silvolu]

Agree with you we should be permissive, unless we do something like registering kinds (as proposed in googleapis/google-cloud-node#157), and then we'd want to enforce a schema.
That proposal is currently blocked on the feature being implemented in the API itself.

[jgeewax]

/cc @GoogleCloudPlatform/cloud-datastore

[pcostell]

The next version of the API will have an explicit null value. So something to consider is that if entity[...] returns nil, there will be no way to distinguish between a set null value and a missing value.

[blowmage]

For the past month or so I've been thinking about differentiating between and entity not having a property vs. having a property with a NULL value. Closely related is how to remove a property from an entity vs. setting the property's value to NULL. First, a bit of background. Currently the Entity has a properties method that returns an array of arrays of the properties and values. But this is a read-only list, and modifications aren't possible.

entity["name"] = "Mike"
entity["email"] = "[email protected]"
entity.properties #=> [["name", "Mike"], ["email", "[email protected]"]]
entity.properties.clear #=> []
entity.properties #=> [["name", "Mike"], ["email", "[email protected]"]]

I'd like to change properties to return a hash-like object that can be inspected and modified:

entity["name"] = "Mike"
entity["email"] = "[email protected]"
entity.properties #=> {"name" => "Mike", "email" => "[email protected]"}

# Check for a property that exists
entity.properties.exist? "name" #=> true
entity["name"] #=> "Mike"
entity.properties["name"] #=> "Mike"

# Check for a property that does not exist
entity.properties.exist? "age" #=> false
entity["age"] #=> nil
entity.properties["age"] #=> nil

# Deleting a property
entity.properties.exist? "email" #=> true
entity.properties.delete "email"
entity.properties.exist? "email" #=> false
entity.properties #=> {"name" => "Mike"}

Here is the my proposed API for this new property object:

• PropertyStore#[] key
• PropertyStore#[]= key, value
• PropertyStore#read key
• PropertyStore#write key, value
• PropertyStore#exist? key
• PropertyStore#fetch key, &block
• PropertyStore#delete key, &block
• PropertyStore#each

This object would also be responsible for normalizing keys to make sure they were always stored as strings but could be accessed as symbols.

entity[:name] = "Mike"
entity[:email] = "[email protected]"
entity.properties.exist? :name #=> true
entity.properties.exist? "name" #=> true
entity.properties #=> {"name" => "Mike", "email" => "[email protected]"}

In the future I can also see this object being responsible for dirty tracking changes, so we don't have to update every property when saving an entity, only the properties that changed. This would be API-compatible with ActiveModel's dirty tracking. Thoughts?

[jgeewax]

👍 from me.

[blowmage]

Please see #62.