[DOC] Parse options doc #3360
Merged
[DOC] Parse options doc #3360
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
|
Thank you for opening this! I apologize for not having made time to review this yet. I will do so in the next few days! |
flavorjones
reviewed
Jan 19, 2025
flavorjones
force-pushed
the
parse_options_doc
branch
from
9731e5e to
00fd1e1
Compare
flavorjones
approved these changes
Jan 22, 2025
|
Thank you so much, @BurdetteLamar! |
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.
What problem is this PR intended to solve?
Improvements to doc for XML::ParseOptions.
Have you included adequate test coverage?
N/A. All doc.
Does this change affect the behavior of either the C or the Java implementations?
No.