Add ADR for using Mobility's table backend#226
Merged
DavidBiddle merged 2 commits intomainfrom Sep 15, 2025
Merged
Conversation
ce26e19 to
f12600b
Compare
theseanything
approved these changes
Sep 8, 2025
Contributor
|
Does this mean we'll need to do a data migration for moving existing content into the translations table? |
Contributor
Author
|
@lfdebrux I don't think a data migration for our existing content is strictly required, but it would make our lives easier in the long run |
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
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.
What
We previously made an ADR proposing using the Mobility gem with its
:columnbackend (#213).This PR adds a new ADR changing our approach to use a different Mobility backend (:table) - we think this will reduce the amount of effort overall.
How to review
Who can review
Any dev other than @DavidBiddle