Feature request:
so far, newly added fields have been optional, and the value ranges of fields have only been extended. This generally allows us to maintain forward compatibility.
However, if we encounter changes in the future that unavoidably break forward compatibility, should we establish a formal version management and compatibility strategy?
Use case:
Feature request:
so far, newly added fields have been optional, and the value ranges of fields have only been extended. This generally allows us to maintain forward compatibility.
However, if we encounter changes in the future that unavoidably break forward compatibility, should we establish a formal version management and compatibility strategy?
Use case: