Fix issue #90: Prevent user from joining or leading more than one hike at a time #392
Conversation
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
Member
|
@jsndz Why do we need this feature? |
Author
|
prevents scheduling conflicts and overlapping responsibilities. And i think it is better to have this constraints so that the group's safety wont be compromised. |
Member
|
Doesn't make much sense to me. I might need a solid reason with a real time usecase to get convinced. |
Author
|
well if a user joins a hike at 9 am and the hike doesn't end till 1 pm he should not be allowed to join any other hike in between that time period since he can't be at 2 places |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR fixes the issue where users could join or lead more than one hike at a time.
Changes
Fixes #90: Prevent user from joining or leading more than one hike at a time.