@FetchOne: Automatically observe primary-keyed records - #519
Merged
Conversation
Right now a `@FetchOne` merely fetches the first row of a table, meaning
if you forget to initialize it with a query, it could reload with the
wrong data (simply the first row of the table):
```swift
struct ProfileView: View {
@FetchOne var profile: Profile
init(profile: Profile) {
_profile = FetchOne(wrappedValue: profile, Profile.find(profile.id))
}
var body: some View { /* ... */ }
}
```
To avoid this bug, let's bake this behavior into `@FetchOne`.
mbrandonw
approved these changes
Aug 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Right now a
@FetchOnemerely fetches the first row of a table, meaning if you forget to initialize it with a query, it could reload with the wrong data (simply the first row of the table):To avoid this bug, let's bake this behavior into
@FetchOne.