Added clarification on type attribute for content items #397
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
10up Block Components
|
||||||||||||||||||||||||||||
| Project |
10up Block Components
|
| Branch Review |
feature/content-picker-readme
|
| Run status |
|
| Run duration | 05m 09s |
| Commit |
|
| Committer | Pete Nelson |
| View all properties for this run ↗︎ | |
| Test results | |
|---|---|
Failures
|
0
|
Flaky
|
0
|
Pending
|
0
|
Skipped
|
0
|
Passing
|
35
|
| View all changes introduced in this branch ↗︎ | |
fabiankaegy
approved these changes
Sep 23, 2025
Member
fabiankaegy
left a comment
fabiankaegy
left a comment
There was a problem hiding this comment.
Thanks for the addition :)
fabiankaegy
added
the
[Type] Documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Added clarification for the
typeattribute for thecontentitems. While I was working on this with a custom post type, I was running into an "Item no longer exists" error and was finally able to resolve it by using the same custom post type that I was using for thecontentTypesparameter, rather than trying to match what I was using for themodeparameter.