-
Notifications
You must be signed in to change notification settings - Fork 125
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
Fixes #165 - Enable documentation comment validation in swift-format #188
Fixes #165 - Enable documentation comment validation in swift-format #188
Conversation
Sorry if the issue wasn't clear, part of the enablement will likely need to be to actually update all the places where the docs aren't passing validation. Otherwise our CI would go red. |
There is also this rule: BeginDocumentationCommentWithOneLineSummary that is comment related, currently set to false. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will need updating the actual places missing docs (try running ./scripts/soundness
locally). That might be quite a bit of work, so if that seems like too much, feel free to put the issue back into the queue and someone else will pick it up later.
I don't think we need to set that, it's overly strict about the abstract of each symbol. Could be added later. |
Just setting the PR back to draft to communicate its status. |
Just a heads up to let you know that I'm still working on it, it will take a little bit of time. |
No rush, @PARAIPAN9 – thanks 🙏 |
Hello, I have another update about this PR. I've come to a stage where I need to include comment documentation for the generated files and by doing this there is reference test that is failing. What would be the best approach here? Should I modify the generator to produce the documentation, similar to how it does it for "Remark" comments? |
No, let's exclude the files from being reformatted and linted. They get formatted as part of the generation process anyway, so this doesn't remove any value. I suspect updating the script for formatting should do the trick. |
…lidation-in-swift-format
@PARAIPAN9 Once you'd like this reviewed, please move the PR into Ready for review. |
Hello @czechboy0, I will update the branch and after I will also change the status. |
…lidation-in-swift-format
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one question about the script, otherwise looks great, thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, @PARAIPAN9!
@PARAIPAN9 If you'd be interested, it'd be good to get this change into swift-openapi-runtime (and the urlsession/ahc transports) as well, but no pressure 🙂 |
Sure, no problem!! |
Motivation
This is for better documentation
Fixes #165
Modifications
Enabled some rules in .swift-format
Result
The .swift-format will be changed and the rules will reflect into the project
Test Plan
Run tests and CI