-
-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOC] Doc for XML::ParseOptions #3347
[DOC] Doc for XML::ParseOptions #3347
Conversation
Thank you for taking the time to improve these docs! I'll make some time to do fact-checking but after a quick pass this looks like a huge improvement. ♥ |
Couple of things.
At first I had a table, and so used GHFM table (and therefore markdown instead of rdoc format). Will change back to rdoc if you like.
I've omitted remarks about which options are defaults for which methods, thinking that the best place to do that is in the methods' own docs. Those call-seqs need adjustments about options defaults; should those be in this PR (or can they wait)?
On Friday, November 29, 2024 at 08:56:23 AM CST, Mike Dalessio ***@***.***> wrote:
Thank you for taking the time to improve these docs! I'll make some time to do fact-checking but after a quick pass this looks like a huge improvement. ♥
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@flavorjones, I'd like to close this and put up a revision of this later on. I've also been working on a new page ( |
@BurdetteLamar OK! Also please see #3355 which is where a great deal of documentation has been updated for the keyword arguments. |
Thanks, @flavorjones. When/where/how do I get access to the updated call-seqs (so I can run examples using the new keyword arguments)? |
@BurdetteLamar Hoping to release v1.17.0 today. |
@flavorjones Outstanding! |
Revises the documentation for
XML::ParseOptions
.