-
Notifications
You must be signed in to change notification settings - Fork 179
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
Utility for generating 'providers.md' #297
Utility for generating 'providers.md' #297
Conversation
Codecov Report
@@ Coverage Diff @@
## master #297 +/- ##
=========================================
Coverage 94.86% 94.86%
- Complexity 1893 1894 +1
=========================================
Files 197 197
Lines 3797 3797
Branches 379 379
=========================================
Hits 3602 3602
Misses 99 99
Partials 96 96 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
That looks very interesting. Nice work, this would be really nice to have to update the documentation with! |
Co-authored-by: Sergey Nuyanzin <sergey.nuyanzin@aiven.io>
How about introducing a file with descriptions of providers |
Why can't it be done in same javadoc with something like |
yes, your idea is better |
Writing description in |
Didn't get what you mean.... could you elaborate please? I mean something like this
|
No, ideally don't do that (introducing a new file or that syntax with @description. The javadoc as-is is fine imo, please just use that, and don't introduce something special for this, unless there's a really good reason for that, which at the moment I don't see. |
…een capitalized letters
everything looks good to me, what do you think? I think it's ready for merge |
Co-authored-by: Sergey Nuyanzin <sergey.nuyanzin@aiven.io>
Regexp does not work properly private String matchSinceTag(String javaDocComment) {
Matcher comment = pattern.matcher(javaDocComment);
if (comment.find()) {
return comment.group().substring("@since".length()).trim();
}
return "";
} |
ok from my point of view it looks more or less ok
@bodiam do you have anything to add? |
I'm following it from the side lines, but I think you've covered everything. I don't mind the output location that much, but I think something in the target directory is probably better, or, if you're feeling confident, just overwrite the actual page in the docs. |
I'm thinking of making a new release, is there anything open on this PR? |
@bodiam Currently, this utility doesn't include descriptions as in the original one (CNPFJ, CPF, and Mountains), so you need manually copy them. And, because of that, it's not recommended to rewrite the original |
@panilya Awesome, I'll fix that. The code is a bit strange at some places, for example the
which is a bit of a mouth full. So, instead, it would probably be better to give this method task: either extract comments form the Javadoc, or keep track of files which don't have a There's really no need to change this, I really appreciate your work on this, but it's just some feedback for in the future, and part of SOLID/SRP(Single Responsibility Pattern), which might be good reading material if you feel like it. |
At that moment, it doesn't support the descriptions. I will add later