-
Notifications
You must be signed in to change notification settings - Fork 346
Modify docs to put error conditions into Errors
sections
#314
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
Comments
Hey brson, first time contributing and really new to rust. I would be happy to help out with this, is this still open? Also I'm afraid I'll need a bit of more info as per which RFC you mean and what exactly the needed changes are. Thanks |
@llompartg thanks, this is still open. He is referring to this guideline. |
Awesome @llompartg! @dtolnay has the link. Basically, every method that returns errors, instead of the error condition being described in the main body of the docs (or not described at all) there should be a section like
|
@llompartg I have just submitted a PR. If you still want to work on this issue, I can close it! (since there is no activity for a while now, so I thought I can submit something). As you want! @brson I still need some mentoring, I'm not sure about my PR quality. |
Add error documentation on parse function See: #314 This is just a try, feel free to close or comment if it's not good. I just submit one error documentation because I want to clearly understand what's the pattern before submitting more documentation: I still have to learn, so I prefer just trying on one function for now (but I can help after that) <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/rust-url/379) <!-- Reviewable:end -->
@rap2hpoutre looks like your pr was merged. Thanks! |
Per rust documentation RFC.
The text was updated successfully, but these errors were encountered: