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
There is a lot of talking of how the schemas can nicely evolve.
But do we have some test or heavily enforced prinicple that the serialized format of a flatbuffer can be read by all versions (or at least is backward compatible)?
This might be especially important for situations when someone saves the messages on disk or connects services which might happen to rely on different (potentially very old) flatbuffer versions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There is a lot of talking of how the schemas can nicely evolve.
But do we have some test or heavily enforced prinicple that the serialized format of a flatbuffer can be read by all versions (or at least is backward compatible)?
This might be especially important for situations when someone saves the messages on disk or connects services which might happen to rely on different (potentially very old) flatbuffer versions.
Beta Was this translation helpful? Give feedback.
All reactions