From f72e63c776fd6a4e5aef125210ba59a3b633ddad Mon Sep 17 00:00:00 2001 From: lsaudon Date: Wed, 27 Oct 2021 10:10:25 +0200 Subject: [PATCH] Fix naming Put the same term everywhere, in accordance with the "Setup" part. --- docs/pages/docs/Advanced Features/migrations.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/pages/docs/Advanced Features/migrations.md b/docs/pages/docs/Advanced Features/migrations.md index 739f19b4..d3f59b09 100644 --- a/docs/pages/docs/Advanced Features/migrations.md +++ b/docs/pages/docs/Advanced Features/migrations.md @@ -303,7 +303,7 @@ You can put this test code whereever you want, but it makes sense to put it in a If we wanted to write them to `test/generated_migrations/`, we could use ``` -$ dart run drift_dev schema generate drift_schemas/ test/generated/ +$ dart run drift_dev schema generate drift_schemas/ test/generated_migrations/ ``` ### Writing tests @@ -317,7 +317,7 @@ import 'package:test/test.dart'; import 'package:drift_dev/api/migrations.dart'; // The generated directory from before. -import 'generated/schema.dart'; +import 'generated_migrations/schema.dart'; void main() { SchemaVerifier verifier; @@ -375,8 +375,8 @@ command. Then, you can import the generated classes with an alias: ```dart -import 'generated/schema_v1.dart' as v1; -import 'generated/schema_v2.dart' as v2; +import 'generated_migrations/schema_v1.dart' as v1; +import 'generated_migrations/schema_v2.dart' as v2; ``` This can then be used to manually create and verify data at a specific version: