solidusio/solidus

Compact migrations into a single one

Open

#5,030 opened on Apr 19, 2023

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Ruby (4,804 stars) (1,270 forks)batch import
good first issuetype:enhancement

Description

Similarly to what we have done with https://github.com/solidusio/solidus/blob/5111949aef306ab0ad2c0b9b61af2e1e26fd2f0d/core/db/migrate/20160101010000_solidus_one_four.rb, we can compact the majority of our migrations into a single one.

This will reduce the number of migrations we copy over the host application.

Contributor guide

Tech stack
rubysql
Domain
backenddatabase
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Ruby on Rails basicsActiveRecord migrationsSolidus project structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Start by studying the example migration at https://github.com/solidusio/solidus/blob/5111949aef306ab0ad2c0b9b61af2e1e26fd2f0d/core/db/migrate/20160101010000 solidus one four.rb to understand the format. Then review all current migrations in the core/db/migrate directory to identify which ones can be consolidated. Pay attention to dependencies between migrations, ensuring no data loss or breaking changes. Check the issue comments for any additional context.