-
-
Notifications
You must be signed in to change notification settings - Fork 8
Fix case-insensitive rank name matching in format lookup #200
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
base: master
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @vLuckyyy, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a significant improvement to how chat formats are retrieved based on a player's rank. By implementing case-insensitive matching for rank names, it makes the system more robust and user-friendly, preventing issues that could arise from inconsistent casing in rank configurations. The change primarily involves modifying the format lookup logic and updating relevant documentation. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request correctly implements case-insensitive matching for rank formats, which is a good improvement. However, the current implementation introduces a performance issue by iterating through all formats for every chat message. I've provided a suggestion to optimize this by using a cached, case-insensitive map for lookups, which restores efficient lookups for format retrieval.
| public String getRawFormat(String rank) { | ||
| return this.format.getOrDefault(rank, this.defaultFormat); | ||
| if (rank == null) { | ||
| return this.defaultFormat; | ||
| } | ||
|
|
||
| String normalizedRank = rank.toLowerCase(); | ||
|
|
||
| for (Map.Entry<String, String> entry : this.format.entrySet()) { | ||
| if (entry.getKey().toLowerCase().equals(normalizedRank)) { | ||
| return entry.getValue(); | ||
| } | ||
| } | ||
|
|
||
| return this.defaultFormat; | ||
| } |
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 implementation correctly provides case-insensitive matching, but it introduces a performance regression. The getRawFormat method now iterates through all configured formats for every call, resulting in an O(N) complexity. Since this method is likely called for every chat message, this can impact server performance.
A more efficient approach is to use a case-insensitive map for lookups. You can create a cached map that is built once and then reused for fast lookups.
First, add a transient field for the cache to the PluginConfig class:
private transient java.util.Map<String, String> lowerCaseFormatCache;Then, update getRawFormat to use this lazy-initialized cache. This will build the cache on the first call and provide fast lookups for all subsequent calls.
Note: If your plugin supports configuration hot-reloading, ensure you invalidate this cache (by setting lowerCaseFormatCache = null;) when the configuration is reloaded to prevent serving stale data.
public String getRawFormat(String rank) {
if (this.lowerCaseFormatCache == null) {
this.lowerCaseFormatCache = new java.util.TreeMap<>(String.CASE_INSENSITIVE_ORDER);
this.lowerCaseFormatCache.putAll(this.format);
}
if (rank == null) {
return this.defaultFormat;
}
return this.lowerCaseFormatCache.getOrDefault(rank, this.defaultFormat);
}
No description provided.