-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
add optional rank at modules domain #11724
Merged
pascalgrimaud
merged 2 commits into
jhipster:main
from
renanfranca:10934-add-optional-rank-at-modules
Jan 25, 2025
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
35 changes: 35 additions & 0 deletions
35
src/main/java/tech/jhipster/lite/module/domain/resource/JHipsterModuleRank.java
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
package tech.jhipster.lite.module.domain.resource; | ||
|
||
/** | ||
* Represents the maturity and adoption level of JHipster modules. | ||
* Ranks range from experimental to community-validated, | ||
* helping users assess module stability and production readiness. | ||
*/ | ||
public enum JHipsterModuleRank { | ||
/** | ||
* Experimental or advanced module requiring specific expertise | ||
*/ | ||
RANK_D, | ||
|
||
/** | ||
* Module without known production usage | ||
*/ | ||
RANK_C, | ||
|
||
/** | ||
* Module with at least one confirmed production usage | ||
*/ | ||
RANK_B, | ||
|
||
/** | ||
* Module with multiple production usages across different projects | ||
* and documented through talks, books or blog posts | ||
*/ | ||
RANK_A, | ||
|
||
/** | ||
* Production-proven module providing unique features, | ||
* validated by community feedback (10+ endorsements) | ||
*/ | ||
RANK_S, | ||
} |
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
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
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
Oops, something went wrong.
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.
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.
not sure we should keep all these comments, as we'll need to update them, as soon as there are some change.
For example: as soon as kipe-authorization change his RANK, the comment here won't be correct
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.
@pascalgrimaud: I agree that the comments weren't timeless. I improved the comment descriptions. I am trying to keep the comments because it is hard to understand rank usage, and I think the enum is the best place to explain it.
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.
I'm also a bit sceptical about these rank usages that are very subjective, so I'm curious to see how this will turn out :)
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.
In my understanding, the ranks are curated by the jhipster lite developers to guide those who are using the tool for the first time. Let's give a try ;)
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.
It will not impact the final user, as we'll always display by default "ALL RANK".
Then, for example, the user can select the RANK_S to display only the most used modules. I don't think he/she'll be unhappy because his prefered module is not displayed in RANK_S, because his module will always be in "ALL RANK", so I'm fine with this
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.
@pascalgrimaud : when you have the time, please, let me know if I can keep these improved comments. Thanks :)