fix: type TypeWithVersion missing latest property #14676
Merged
Conversation
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
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖 |
jessrynkar
approved these changes
Nov 19, 2025
Contributor
|
🚀 This is included in version v3.65.0 |
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.
What?
Adds the missing
latest?: booleanproperty to theTypeWithVersion<T>type definition.Why?
The
latestproperty is set by database adapters when creating and updating versions (both collection and global versions), and is included in the version field schema when drafts are enabled. However, it was missing from the TypeScript type definition, causing type errors when consumers try to access this property on version documents.How?
Added
latest?: booleanas an optional property to theTypeWithVersion<T>type. The property is optional because it's only present when drafts are enabled in the version configuration.Fixes #14624