-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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.
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
chore(richtext-lexical): improve types of UploadData #10982
Open
GermanJablo
wants to merge
3
commits into
main
Choose a base branch
from
UploadData
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,7 +8,7 @@ import type { | |
NodeKey, | ||
Spread, | ||
} from 'lexical' | ||
import type { CollectionSlug, DataFromCollectionSlug, JsonObject } from 'payload' | ||
import type { FileData, JsonObject, TypedCollection, TypeWithID } from 'payload' | ||
import type { JSX } from 'react' | ||
|
||
import { DecoratorBlockNode } from '@lexical/react/LexicalDecoratorBlockNode.js' | ||
|
@@ -17,15 +17,27 @@ import { $applyNodeReplacement } from 'lexical' | |
import * as React from 'react' | ||
|
||
export type UploadData<TUploadExtraFieldsData extends JsonObject = JsonObject> = { | ||
[TCollectionSlug in CollectionSlug]: { | ||
fields: TUploadExtraFieldsData | ||
// Every lexical node that has sub-fields needs to have a unique ID. This is the ID of this upload node, not the ID of the linked upload document | ||
id: string | ||
relationTo: TCollectionSlug | ||
// Value can be just the document ID, or the full, populated document | ||
value: DataFromCollectionSlug<TCollectionSlug> | number | string | ||
} | ||
}[CollectionSlug] | ||
fields: TUploadExtraFieldsData | ||
/** Every lexical node that has sub-fields needs to have a unique ID. This is the ID of this upload node, not the ID of the linked upload document */ | ||
id: string | ||
relationTo: string | ||
/** Value can be just the document ID, or the full, populated document */ | ||
value: number | string | TypedCollection | ||
} | ||
|
||
/** | ||
* UploadData_P4 is a more precise type, and will replace UploadData in Payload v4. | ||
* I am not encouraging users to use this type via tsdoc yet, in case we find more breaking changes to do prior to v4. | ||
GermanJablo marked this conversation as resolved.
Show resolved
Hide resolved
|
||
* @internal | ||
*/ | ||
export type UploadData_P4<TUploadExtraFieldsData extends JsonObject = JsonObject> = { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same as above on |
||
fields: TUploadExtraFieldsData | ||
// Every lexical node that has sub-fields needs to have a unique ID. This is the ID of this upload node, not the ID of the linked upload document | ||
id: string | ||
relationTo: string | ||
// Value can be just the document ID, or the full, populated document | ||
value: (FileData & TypeWithID) | number | string | ||
} | ||
|
||
export function isGoogleDocCheckboxImg(img: HTMLImageElement): boolean { | ||
return ( | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this naming convention? Feels like
_P4
doesn't feel meaningful. What is the intent?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As the comment says, this is to indicate that it will be the type in Payload v4. I originally used
_V4
, but changed it to_P4
so that no one thinks it is the version of this type, but the version of Payload.Alternatively I could use
_Payload_V4
or_Payload_v4
. Any preferences?