feat!: add InfoType enum for PostalInfo.info_type
#50
Conversation
This file contains hidden or 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
djc
approved these changes
Oct 19, 2024
Merged
Owner
|
Thanks, this seems nice! I proactively bumped the version to 0.5.0 in #51 because this change is semver-incompatible. |
Contributor
Author
|
thanks |
Owner
I'm not that familiar with that standard, so after we've released 0.5.0 please just call it out explicitly in the PR description. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
From RFC 5733 - EPP Contact Mapping:
"Two elements are provided so that address information can be
provided in both internationalized and localized forms ... If an
internationalized form (type="int") is provided, ... If a localized form
(type="loc") is provided ..."