Swap around checking of VENUE and LOCATION content #27
Conversation
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
senpos
reviewed
Mar 25, 2018
| @@ -95,10 +95,10 @@ def content_type(self): | |||
| return ContentType.VOICE[0] | |||
| if self.contact: | |||
| return ContentType.CONTACT[0] | |||
| if self.location: | |||
| return ContentType.LOCATION[0] | |||
| if self.venue: | |||
There was a problem hiding this comment.
Since Venue contains location and venue properties, isn't it better to check for both of them, rather than rely on checks positioning in the code?
if self.location:
if self.venue:
return ContentType.VENUE[0]
return ContentType.LOCATION[0]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix for issue #26
Venue Message consists of location and venue fields.
If you check location first - you always set message type = location