aboutsummaryrefslogtreecommitdiffstats
path: root/docs/explanation.md
diff options
context:
space:
mode:
authorEugene Triguba <hello@eugenetriguba.com>2025-10-11 00:01:28 -0400
committerEugene Triguba <hello@eugenetriguba.com>2025-10-11 00:01:28 -0400
commit9ef8b85e372fd23d1e4ff615e438e8e51acad3bf (patch)
tree1f032744da541396ae66f4cd95f7bae02cacd349 /docs/explanation.md
parentReword tradeoffs for version styles (diff)
downloadcli-9ef8b85e372fd23d1e4ff615e438e8e51acad3bf.zip
Fix a few bullets in explanation.md
Diffstat (limited to 'docs/explanation.md')
-rw-r--r--docs/explanation.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/explanation.md b/docs/explanation.md
index 1d1393b..469a5e6 100644
--- a/docs/explanation.md
+++ b/docs/explanation.md
@@ -176,6 +176,7 @@ Bolt needs to sort migrations to determine the correct application order. Consid
```
How should these be sorted? As strings:
+
- `001` comes before `002` comes before `20240316145038` ✓
But what if you had:
@@ -186,9 +187,11 @@ But what if you had:
```
Now the string sorting would be:
+
- `001`, then `002`, then `20240316145038`
But the chronological creation order was:
+
- `001`, then `20240316145038`, then `002`
This creates ambiguity about the intended order.
@@ -196,6 +199,7 @@ This creates ambiguity about the intended order.
### Parsing Complexity
Bolt parses version numbers according to the configured version style:
+
- **Timestamp style**: Expects exactly 14 digits in `YYYYMMDDHHMMSS` format
- **Sequential style**: Expects an integer (any length)