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
As you can see in the Protocol buffers specification is possible to define non-scalar properties as you can see here.
What if the MVT specification includes that kind of options in the Values part to be able to pass array-based or composite properties that could be used for different purposes like for example interactivity.
I assume that in the past this was not added to the specification because the version 2 of the protocol buffers didn't support it, the version 3 was released the 26th of July, 2016 and the last change in the .proto file for MVT was the 5th June 2016 but now we are able to use if assuming the 3.0 proto version is going to use the proto3 Spec :)
The text was updated successfully, but these errors were encountered:
As you can see in the Protocol buffers specification is possible to define non-scalar properties as you can see here.
What if the MVT specification includes that kind of options in the
Values
part to be able to pass array-based or composite properties that could be used for different purposes like for example interactivity.I assume that in the past this was not added to the specification because the version 2 of the protocol buffers didn't support it, the version 3 was released the 26th of July, 2016 and the last change in the .proto file for MVT was the 5th June 2016 but now we are able to use if assuming the 3.0 proto version is going to use the proto3 Spec :)
The text was updated successfully, but these errors were encountered: