changed service areas to be a many to many #870
Merged
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
Co-authored-by: maebeale <maebeale@gmail.com> Co-authored-by: exbinary <exbinary@gmail.com> Co-authored-by: connieh1 <connie2630a@gmail.com>
maebeale
approved these changes
Mar 3, 2021
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.
Co-authored-by: maebeale maebeale@gmail.com
Co-authored-by: exbinary exbinary@gmail.com
Co-authored-by: connieh1 connie2630a@gmail.com
Why
Community Resource can have multiple service areas so we changed the relationship to be a many to many by creating a CommunityResourceServiceArea as a join
Pre-Merge Checklist