Improve Enum documentation #63
Merged
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
ARCA-264 ARCA-265 arcalot#57: The link to the Enums section is broken. arcalot#58: Clarify semantics and use of Enums in Python and Arcaflow. resolves arcalot#58 resolves arcalot#57
mfleader
approved these changes
Sep 18, 2023
jaredoconnell
approved these changes
Sep 18, 2023
|
This is good until/if we get any more examples showing that the explicit string or int enum types are required. And there's a good chance that in those cases, it's a bug, rather than something that needs documentation changes. |
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.
Corrected the link
Streamlined and clarified, I think, but there's no evidence that an explicit sub-type, which essentially would change the default
__str__method, is necessary. I'm assuming that, if this is incorrect, this PR will solicit a relevant response!resolves #58
resolves #57
By contributing to this repository, I agree to the contribution guidelines.