Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Capabilities <-> Actor association change to many-to-many #360

Merged
merged 2 commits into from
Nov 14, 2024
Merged

Capabilities <-> Actor association change to many-to-many #360

merged 2 commits into from
Nov 14, 2024

Conversation

mromulus
Copy link
Collaborator

  • feat: Add data migrations gem
  • feat: Change Capability <-> Actor relation to many-to-many

@mromulus
feat: Add data migrations gem
e769b4c 
This avoids messy and hacky additions in regular migrations
@mromulus
feat: Change Capability <-> Actor relation to many-to-many
fa94a5b 
By requirements in real exercises, sometimes capabilities should be tied
to more than one actor. As this association is mostly for grouping
purposes, there are no big logic changes, just adapting UI and making
sure tests pass.
@mromulus mromulus added enhancement New feature or request data model change Changes in DB schema/data model labels Nov 14, 2024
@mromulus mromulus self-assigned this Nov 14, 2024
@mromulus mromulus merged commit fa94a5b into main Nov 14, 2024
2 checks passed
@mromulus mromulus deleted the cap_habtm branch November 14, 2024 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@mromulus mromulus

Labels
data model change Changes in DB schema/data model enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@mromulus