Skip to content

Update 2023-05-17-enhanced-ergonomics-for-record-types.mdx #689

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
merged 2 commits into from
May 22, 2023
Merged

Update 2023-05-17-enhanced-ergonomics-for-record-types.mdx #689

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
16d8343
Update 2023-05-17-enhanced-ergonomics-for-record-types.mdx
cristianoc May 21, 2023
ba345c0
Update 2023-05-17-enhanced-ergonomics-for-record-types.mdx
cristianoc May 22, 2023
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
2 changes: 1 addition & 1 deletion _blogposts/2023-05-17-enhanced-ergonomics-for-record-types.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ type c = {
}
```

Keeping it as straightforward as possible, type spreads are essentially a "copy-paste" operation for fields from one or more records to another, inlining the fields from the spread records into the new record. Please note: As for right now it is not possible to override fields in the target record type.
Record type spreads act as a 'copy-paste' mechanism for fields from one or more records into a new record. This operation inlines the fields from the spread records directly into the new record definition, while preserving their original properties, such as whether they are optional or mandatory. It's important to note that duplicate field names are not allowed across the records being spread, even if the fields share the same type.

Needless to say, this feature offers a much better ergonomics when working with types with lots of fields, where variations of the same underlying type are needed.

Expand Down