Adding documentation for the proto2 incompatibility #321
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'd say this PR partially closes #162. TBH, today was my first day poking around with Skeuomorph, and I don't know enough about the existing design tradeoffs to know the extent of the incompatibilities between our library and the existing schema protocols. However, we do have one open issue (#218) that mentions the incompatibility between Proto3 and Proto2, and in lieu of changing the design of skeuomorph to support both protobuf protocols, adding the documentation around this behavior is a good first step in helping our users understand the intentional incompatibilities herein.
Super open to suggestions about what other known Skeuomorph incompatibilities exist, and would be happy to address them in this PR.