unchuckable opened a new pull request #1067:
URL: https://github.com/apache/avro/pull/1067


   Sorry this took a little. Corona and RL made me have to deal with other 
issues before this one.
   Feedback welcome. I tried to provide the functionality of AVRO-1329 along 
with some suitable yet compatible changes to the public API, but am well 
willing to make changes as deemed appropriate.
   
   Thanks, and stay safe.
   
   ---8<------
   
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [X] My PR addresses the following [Avro 
Jira](https://issues.apache.org/jira/browse/AVRO/) issues and references them 
in the PR title. For example, "AVRO-1234: My Avro PR"
     - https://issues.apache.org/jira/browse/AVRO-1329
   
   
   ### Tests
   
   - [X] My PR adds the following unit tests:
    - TestSchema.testExtendedEnumSchemaSerializeAndDeserialize
    - TestSchema.testSimpleEnumSchemaSerialize
    - Updates/Extensions to Compiler Unit tests
   
   ### Commits
   
   - [X] My commits all reference Jira issues in their subject lines. In 
addition, my commits follow the guidelines from "[How to write a good git 
commit message](https://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [X] In case of new functionality, my PR adds documentation that describes 
how to use it.
     - All the public functions and the classes in the PR contain Javadoc that 
explain what it does
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to