Skip to content

docs: Require nullable for scoped model fields and fix example #681

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
developerjamiu merged 1 commit into from
Jul 9, 2026
Merged

docs: Require nullable for scoped model fields and fix example #681

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/06-concepts/02-models/01-models.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ fields:
hiddenSecretKey: String
```

It is also possible to set a `scope` on a per-field basis. By default all fields are visible to both the server and the client. The available scopes are `all`, `serverOnly`, `none`.
It is also possible to set a `scope` on a per-field basis. By default all fields are visible to both the server and the client. The available scopes are `all`, `serverOnly`, `none`. A field with a scope other than `all` must be nullable.

:::info
**none** is not typically used in serverpod apps. It is intended for the serverpod framework, itself.
Expand All @@ -62,7 +62,7 @@ It is also possible to set a `scope` on a per-field basis. By default all fields
```yaml
class: SelectivelyHiddenClass
fields:
hiddenSecretKey: String, scope=serverOnly
hiddenSecretKey: String?, scope=serverOnly
publicKey: String
```

Expand Down
Loading