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.
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
feat: add determine appid+cluster namespace num limit logic #5228
feat: add determine appid+cluster namespace num limit logic #5228
Changes from all commits
4d29c26
abb9a20
2195d79
4ae8bee
a946ad1
e562606
cded46c
2ccd935
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
🛠️ Refactor suggestion
Improve exception handling in testNamespaceNumLimit
The test effectively verifies the namespace number limit functionality. However, the exception handling can be improved for better clarity and specificity.
Consider using JUnit's
assertThrows
method to check for theServiceException
. This will make the test more readable and specific about the expected exception. Here's a suggested refactoring:This refactoring improves readability and makes the test's intention clearer.
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.
🛠️ Refactor suggestion
Improve test setup in testNamespaceNumLimitFalse
The test effectively verifies the behavior when the namespace limit is not enforced. However, it could be improved by explicitly setting
isNamespaceNumLimitEnabled
to false for clarity.Consider adding an explicit mock for
isNamespaceNumLimitEnabled()
. This will make the test's intention clearer. Here's a suggested improvement:This change makes it explicit that the namespace limit is disabled, improving the test's readability and intent.