-
Notifications
You must be signed in to change notification settings - Fork 37
Add TF2 specific player subclass. Add class names and id's to team data #340
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
Closed
Closed
Changes from 1 commit
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
Prev
Previous commit
Fix names
- Loading branch information
commit f070bc4ef9ee0d428c60bb815c97027a708af838
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,7 +30,7 @@ def team_name(self): | |
|
||
@team_name.setter | ||
def team_name(self, team_name): | ||
if team_id not in self._teams_names: | ||
if team_name not in self._teams_names: | ||
raise ValueError(f"Invalid team_name: {team_name}") | ||
|
||
self.team = self._teams_names[team_name] | ||
|
@@ -42,8 +42,8 @@ def player_class_name(self): | |
|
||
@player_class_name.setter | ||
def player_class_name(self, class_name): | ||
if team_id not in self._class_names: | ||
if class_name not in self._class_names: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The dictionary here is queried twice (once through v = d.get(k, None)
# If k wasn't in d, let's raise
if v is None:
raise
... This would ensure the dictionary is looked up only once rather than twice, etc. |
||
raise ValueError(f"Invalid class_name: {class_name}") | ||
|
||
# Does this need to be desired_player_class or should there be a setter for desired class? | ||
self.player_class = self._class_names[team_name] | ||
# Does this need to be desired_player_class or should there b a setter for desired class? | ||
self.player_class = self._class_names[class_name] |
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.
Rather than having multiples
team_name
methods decorated as getter and setter I think it would be better to follow the overall design of the other properties across the whole project where they are distinctly available as methods as well. For example,get_team_name
andset_team_name
bound to theteam_name
property.