Skip to content

Commit 13ce4ee

Browse files
stephencelisgithub-actions[bot]
authored andcommitted
Run swift-format
1 parent 5144ec0 commit 13ce4ee

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Sources/StructuredQueriesCore/Documentation.docc/Articles/DefiningYourSchema.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -309,8 +309,8 @@ And StructuredQueries will take care of formatting the value for the database:
309309
}
310310
}
311311
312-
If you use the non-default date representation in your schema, then while querying against a
313-
date column with a Swift Date, you will need to explicitly bundle up the Swift date into the
312+
If you use the non-default date representation in your schema, then while querying against a
313+
date column with a Swift Date, you will need to explicitly bundle up the Swift date into the
314314
appropriate representation to use various query helpers. This can be done using the `#bind` macro:
315315
316316
```swift
@@ -319,7 +319,7 @@ Reminder.where { $0.created > #bind(startDate) }
319319
320320
> Note: When using the default representation for dates (ISO-8601 text) you do not need to use
321321
> the `#bind` macro:
322-
>
322+
>
323323
> ```swift
324324
> Reminder.where { $0.created > startDate }
325325
> ```
@@ -352,7 +352,7 @@ Reminder.where { $0.id != #bind(reminder.id) }
352352
353353
> Note: When using the default representation for UUID (lower-cased text) you do not need to use
354354
> the `#bind` macro:
355-
>
355+
>
356356
> ```swift
357357
> Reminder.where { $0.id != reminder.id }
358358
> ```

0 commit comments

Comments
 (0)