feat: allow generation of hash functions for optional fields #20
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Amir Omidi <amir@aaomidi.com>
aaomidi
force-pushed
the
amir/support-optional
branch
from
801c4d5
to
0c2193c
Compare
aaomidi
changed the title
|
Any thoughts on getting a release with the latest changes? |
|
I've tagged v0.3.0 so you should be able to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Fixes #19
So this changes all the field accessors to use Get() instead of accessing them directly. Let me know if you think that's undesirable. It was a shortcut I decided to make to reduce the amount of branching the code needs to do for different fields.
Checklist
git commit -s ...) to provide the DCO