From 0c19aa9cc46bbc3def7a23adef778c0ab4dae8c0 Mon Sep 17 00:00:00 2001 From: Shazib Hussain Date: Sat, 25 Nov 2023 00:06:22 +0000 Subject: [PATCH] Update migrations.md --- docs/contributing/project-details/migrations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/contributing/project-details/migrations.md b/docs/contributing/project-details/migrations.md index 707c87f28..7b45ff217 100644 --- a/docs/contributing/project-details/migrations.md +++ b/docs/contributing/project-details/migrations.md @@ -10,6 +10,6 @@ There are some important considerations to make when adding a feature with a db * The naming convention is as follows: `TIMESTAMP_name.sql`. for example. `1694438752000_add_goal_targets.sql` -* It is strongly discouraged to try to remove columns and tables, This makes reverting changes impossible and introduces unneccessary risk when we can simply stop using them in code. +* It is strongly discouraged to try to remove columns and tables, This makes reverting changes impossible and introduces unnecessary risk when we can simply stop using them in code. -* You should be very deliberate with your migration. When adding a feature, try to think about future scenarios and options that may be desired later, so we can minimise the number of migrations. \ No newline at end of file +* You should be very deliberate with your migration. When adding a feature, try to think about future scenarios and options that may be desired later, so we can minimise the number of migrations.