Add polymorphic relationship affiliable to affiliations
#12709
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
db/migrate/20260123011001_validate_add_affiliable_to_affiliations.rb
Outdated
Show resolved
Hide resolved
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.
Summary of the problem
As part of work on #12188, we're going to be adding affiliations to applications. However, since an event is not yet created at this time, we need to make affiliations have a polymorphic relationship to either
EventorEvent::Application. Once the application is approved and the event created, all we'll have to do is switch overaffiliable.Describe your changes
Adds a new
affiliablepolymorphic relationship onEvent::Affiliation. The migration automatically copies over the current linked events and makes the relationship non-null.Controllers and views that work with affiliations have been updated to use the new polymorphic relationship, and the routes for affiliations are now in the root scope instead of being nested inside the events resource.
After this PR is deployed, I'll make a new one to delete the old
eventrelationship.