-
Notifications
You must be signed in to change notification settings - Fork 450
fix(KekkaiActivation):修改结界挂卡逻辑,可使用智能放入 #1655
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
Open
huiyuhang1
wants to merge
1
commit into
runhey:dev
Choose a base branch
from
huiyuhang1:cursor/fix-kekkaiactivation-smart-put-139b
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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
This file contains hidden or 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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or 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 hidden or 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 hidden or 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.
suggestion:
check_max_lv的shikigami_class参数现在已经未被使用,可以考虑移除。由于
check_max_lv已经不再使用shikigami_class,并且调用方也不再传入该参数,继续在函数签名中保留它会具有误导性。请考虑移除该参数,或者为其引入一个有意义的用途(例如在智能放入不可用时作为回退方案),以保持 API 的清晰和准确。建议的实现方式:
check_max_lv的调用。如果仍有调用传入shikigami_class(例如self.check_max_lv(ShikigamiClass.N)),请移除该实参,使其改为调用self.check_max_lv()。shikigami_class后的新函数签名。Original comment in English
suggestion: The
shikigami_classparameter ofcheck_max_lvis now unused and could be removed.Since
check_max_lvno longer usesshikigami_classand callers no longer pass it, keeping the parameter in the signature is misleading. Please either remove it or introduce a meaningful use (e.g., as a fallback when auto-put is unavailable) to keep the API clear and accurate.Suggested implementation:
check_max_lvin the codebase. If any calls still passshikigami_class(e.g.,self.check_max_lv(ShikigamiClass.N)), remove the argument so they callself.check_max_lv()instead.shikigami_class.