feat(nodes): WordPress integration with blog publishing support Closes #33#45
Closed
DheerajShrivastav wants to merge 4 commits into
Closed
feat(nodes): WordPress integration with blog publishing support Closes #33#45DheerajShrivastav wants to merge 4 commits into
DheerajShrivastav wants to merge 4 commits into
Conversation
Closes wespreadjam#33 - Add wordpressCreatePost node — creates a new post via POST /wp-json/wp/v2/posts, defaults to draft status; supports categories, tags, featuredMediaId (mapped to featured_media), excerpt, slug - Add wordpressUpdatePost node — partially updates a post via POST /wp-json/wp/v2/posts/{id}; only sends explicitly provided fields - Add wordpressGetPosts node — fetches posts via GET /wp-json/wp/v2/posts; supports status, perPage (mapped to per_page, capped 1-100), page, search; reads X-WP-Total response header for totalFound; returns { posts, meta: { totalFound, limit, offset } } - Add wordpressCredential using defineBasicCredential with siteUrl, username, applicationPassword fields; Authorization header computed at runtime as Basic base64(username:applicationPassword) - Normalize raw WP REST API snake_case responses to consistent camelCase shape (title.rendered -> title, featured_media -> featuredMedia, etc.) - Support siteUrl subpaths (e.g. https://example.com/blog) and strip trailing slashes before building endpoint URLs - Add wordpress to NodeCredentials interface in core - Register all three nodes in builtInNodes (27 total) - Use fetchWithRetry for all API calls - 43 unit tests: credential metadata, schema validation, normalizer, request shaping, auth header, X-WP-Total parsing, offset computation, subpath/trailing slash handling, missing credentials errors, error responses Co-Authored-By: Claude <noreply@anthropic.com>
…on and index files
Contributor
|
Merged in commit a86d34f. Thank you for the WordPress integration! 🎉 |
Contributor
Author
|
Hey @MAlshaik , thanks so much for merging this and the other PR! I’m really glad the features are helpful. I noticed that for both PRs, the commits were pushed directly to main instead of using GitHub’s merge, so my GitHub profile didn't get the author credit/contribution squares for the work. Since I'm actively trying to build up my open-source profile, would it be possible to use the standard merge button or the --author flag for future PRs? I'd really appreciate it! |
Contributor
|
Hey yes sorry about this i fixed the issue and gave u the author. let me know if there is any problems. |
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
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.
Summary
Implements comprehensive WordPress integration for blog management and media upload.
Closes #33
Features
Implementation Details
wordpressCreatePost, etc.Testing