fix: pictique requiring text on posts

[coodos]

Description of change

Pictique expects all social posts to have text and setting no text causes sync issues.

Issue Number

Type of change

• Fix (a change which fixes an issue)

How the change has been tested

Change checklist

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• Bug Fixes
  • Improved post creation and update processes to properly initialize text fields, ensuring consistent data handling.

[coderabbitai]

Walkthrough

The WebhookController now initializes the text field to an empty string in both post creation and update operations, ensuring the text property is always defined and preventing potential undefined access issues.

Changes

Cohort / File(s)	Change Summary
Webhook Controller Text Field Initialization platforms/pictique-api/src/controllers/WebhookController.ts	Initialize local.data.text to empty string for both new post creation and existing post updates to guarantee text field existence.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

• Single-file change with straightforward initialization logic
• Consistent pattern applied across two scenarios (create and update)
• Minimal risk due to defensive initialization rather than logic alteration

Suggested reviewers

• ananyayaya129
• sosweetham

Poem

🐰 A text field danced through the code so free,
But sometimes undefined it came to be!
Now nestled safe in strings of empty grace,
The webhook's heart finds its true place. ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix: pictique requiring text on posts' accurately and specifically describes the main change—ensuring text fields are initialized to prevent Pictique sync issues.
Description check	✅ Passed	The PR description follows the template structure with issue context, fix categorization, and a completed checklist; however, 'How the change has been tested' section is empty.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/pictique-text-null-error

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7281abd and 76e3cda.

📒 Files selected for processing (1)

• platforms/pictique-api/src/controllers/WebhookController.ts (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build

🔇 Additional comments (1)

platforms/pictique-api/src/controllers/WebhookController.ts (1)

177-177: Let me search with a more specific query:

Let me search more specifically for Pictique as a service:

Cannot verify Pictique API text field requirements—no public documentation available.

The code changes initialize text to an empty string when undefined/null, consistently applied in both update and create paths for posts. However, I was unable to find public documentation for the Pictique API to confirm whether empty strings are accepted for the text field.

Verify with your Pictique account or internal API documentation that the service accepts empty strings for post text fields before deploying this change.

Also applies to: 192-192

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}