You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to talk about handling breaking changes in data schema, e.g. enterprise-contract/ec-policies#1143. Currently, we have to wait until a certain version of the ec policies is propagated in all the places we care about. Otherwise, using a newly supported attribute may cause data schema failures for some users.
The current approach is ok, but I'd rather not have to stage changes together. Can we think of a simpler way to do this?
We could use some convention, e.g. <key>_v2, to represent this. Is that too heavy handed?
Overview
At 10am Eastern, 7am Pacific, 2pm UTC; find your time
Video call link: meet.google.com/ved-ivnv-aen
dial-in: (US) +1 409-444-2447
PIN: 873 550 579#
More phone numbers: tel.meet/ved-ivnv-aen?pin=7872592963542&hs=1
Add topics you'd like to discuss below!
The text was updated successfully, but these errors were encountered: