Skip to content

Add ADR for using Mobility's table backend#226

Merged
DavidBiddle merged 2 commits intomainfrom
add-adr-mobility-table-backend
Sep 15, 2025
Merged

Add ADR for using Mobility's table backend#226
DavidBiddle merged 2 commits intomainfrom
add-adr-mobility-table-backend

Conversation

@DavidBiddle
Copy link
Copy Markdown
Contributor

@DavidBiddle DavidBiddle commented Sep 5, 2025

What

We previously made an ADR proposing using the Mobility gem with its :column backend (#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

  1. Semantic: Do you agree with the changes?
  2. Syntactic: Spelling, grammar, etc.

Who can review

Any dev other than @DavidBiddle

@DavidBiddle DavidBiddle force-pushed the add-adr-mobility-table-backend branch from ce26e19 to f12600b Compare September 8, 2025 09:34
@DavidBiddle DavidBiddle self-assigned this Sep 8, 2025
@DavidBiddle DavidBiddle requested a review from a team September 8, 2025 09:40
@DavidBiddle DavidBiddle marked this pull request as ready for review September 8, 2025 10:00
@lfdebrux
Copy link
Copy Markdown
Contributor

Does this mean we'll need to do a data migration for moving existing content into the translations table?

@DavidBiddle
Copy link
Copy Markdown
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

@DavidBiddle DavidBiddle merged commit 211ee58 into main Sep 15, 2025
2 checks passed
@DavidBiddle DavidBiddle deleted the add-adr-mobility-table-backend branch September 15, 2025 10:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants