{"push_id":643823402,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"bebdf621c5466c72035f5f46a6b1dc838bb80139","before":"c50412ee1e5ae9390eee3e5edad705ba9d98e3e5","commits":[{"sha":"bebdf621c5466c72035f5f46a6b1dc838bb80139","author":{"email":"7453cbd82c48d8acd14153e824a17ee83c61095c@us.ibm.com","name":"Eric Fried"},"message":"Embed traits in entities.Entry and .Element\n\nAPITraits, recently introduced to facilitate cross-version compatibility\nof pypowervm with different REST API servers, are sometimes needed\nwithin Wrapper instances to make decisions as to how certain getters and\nsetters should be implemented.  Because APITraits are linked to the\nSession, the most effective way to trickle them down to Wrapper\ninstances (without requiring the consumer to pass them into the Wrapper\nmethods themselves) is via the following paths:\n\nResponse => Feed => Entry => EntryWrapper\n         => Entry => EntryWrapper\n         => Element => ElementWrapper\n\nThis change set creates the framework and implementation such that a\ngiven ElementWrapper or EntryWrapper instance has a .traits property it\ncan consult to make API-specific decisions.\n\nAlso included three new test fixtures in pypowervm.tests.fixtures (note\nthese are instances, not classes):\n\nLocalPVMTraitsFx\nRemotePVMTraitsFx\nRemoteHMCTraitsFx\n\nChange-Id: I63723a51f229786a42eb9d8193a4516d8d0da15b","distinct":true,"url":"https://api.github.com/repos/pypowervm/pypowervm/commits/bebdf621c5466c72035f5f46a6b1dc838bb80139"}]}