Skip to content

Support editing custom posts#25208

Draft
crazytonyli wants to merge 6 commits intoprototype-custom-post-typesfrom
prototype-custom-post-types-local
Draft

Support editing custom posts#25208
crazytonyli wants to merge 6 commits intoprototype-custom-post-typesfrom
prototype-custom-post-types-local

Conversation

@crazytonyli
Copy link
Contributor

Description

Testing instructions

@dangermattic
Copy link
Collaborator

2 Warnings
⚠️ View files have been modified, but no screenshot or video is included in the pull request. Consider adding some for clarity.
⚠️ This PR is larger than 500 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.
1 Message
📖 This PR is still a Draft: some checks will be skipped.

Generated by 🚫 Danger

@wpmobilebot
Copy link
Contributor

wpmobilebot commented Feb 3, 2026

🤖 Build Failure Analysis

This build has failures. Claude has analyzed them - check the build annotations for details.

Copy link
Member

@dcalhoun dcalhoun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I perceive the draft status and current code to mean this is not ready for formal review. Regardless, I left a few thoughts for consideration from an initial review and testing.

Overall, things seem to operate relatively well. I noted one preexisting bug: CMM-1214

To elaborate on my original request for an integration PR, I primarily wanted to ensure an integration would merge relatively quickly after we merge the GutenbergKit (GBK) PR to avoid breaking changes in the GBK library blocking other GBK work. Sorry if I did not communicate that clearly enough previously. Thank you for beginning this work nonetheless.

.package(url: "https://github.com/wordpress-mobile/NSURL-IDN", revision: "b34794c9a3f32312e1593d4a3d120572afa0d010"),
.package(url: "https://github.com/zendesk/support_sdk_ios", from: "8.0.3"),
.package(url: "https://github.com/wordpress-mobile/GutenbergKit", from: "0.13.1"),
.package(url: "https://github.com/wordpress-mobile/GutenbergKit", revision: "7a48d8756f33e3d25daa1fff5843d5cd6fdda887"),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When we are ready, we can integrate a GBK prerelease. We'll publish the prerelease via make release VERSION_TYPE=preminor DRY_RUN=true on GBK's trunk branch.

let configuration = EditorConfigurationBuilder(
content: initialContent ?? "",
postType: "comment",
postType: .init(postType: "comment", restBase: "comments"), // FIXME: "comment" is not a post type.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we feel compelled to "fix" the post type, we might also consider fixing the site URL and API root. GBK currently requires all of these, but effectively discards them when "offline mode" is enabled.

For context, this comment editor is currently unused.

// otherwise pass nil and GutenbergKit will fetch them (shows progress bar)
let cachedDependencies = EditorDependencyManager.shared.dependencies(for: blog)
var cachedDependencies: EditorDependencies? = nil
if postType == .post || postType == .page {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Attempting to understand this. My perception is that we do not preload specifically for Pages at this time. If true, why might it be OK to apply the cache for Pages, but not other custom post types?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why might it be OK to apply the cache for Pages, but not other custom post types?

That's true. I'll remove the if check.

@crazytonyli
Copy link
Contributor Author

I primarily wanted to ensure an integration would merge relatively quickly after we merge the GutenbergKit (GBK) PR to avoid breaking changes in the GBK library blocking other GBK work.

Absolutely. I will not merge the GBK PR until this PR is ready.

@crazytonyli crazytonyli changed the title Prototype custom post types local Support editing custom posts Feb 4, 2026
@crazytonyli crazytonyli force-pushed the prototype-custom-post-types-local branch from ac6d26f to 6a6c440 Compare February 8, 2026 21:19
@crazytonyli crazytonyli force-pushed the prototype-custom-post-types-local branch from 6a6c440 to 33deb2f Compare February 8, 2026 21:32
@wpmobilebot
Copy link
Contributor

wpmobilebot commented Feb 8, 2026

App Icon📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.
App NameWordPress
ConfigurationRelease-Alpha
Build Number30840
VersionPR #25208
Bundle IDorg.wordpress.alpha
Commit8e6668a
Installation URL3kl8sj5ehok3g
Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

@wpmobilebot
Copy link
Contributor

wpmobilebot commented Feb 8, 2026

App Icon📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.
App NameJetpack
ConfigurationRelease-Alpha
Build Number30840
VersionPR #25208
Bundle IDcom.jetpack.alpha
Commit8e6668a
Installation URL21a91u60gmqko
Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 9, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants