Fix build error

[acicovic]

Description

With this PR, we're attempting to fix this build error in the develop branch.

Summary by CodeRabbit

• Refactor
  • Standardized internal request configuration to set response parsing via safer option handling.
  • Maintains existing behavior for errors, responses, and overall functionality; no user-visible changes.
  • Improves code clarity and future compatibility without altering performance.
  • No action required from users; features continue to work as before.

[coderabbitai]

📝 Walkthrough

Walkthrough

Reworked BaseProvider.fetch to supply parse: true by creating a new options object via spread, replacing a previous type cast to APIFetchOptions. Error handling and response processing remain unchanged. No exported API surface changes.

Changes

Cohort / File(s)	Summary
API fetch options handling src/content-helper/common/providers/base-provider.tsx	Replace type cast with object spread to set parse: true on the api-fetch call; logic and control flow unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Attempt to fix develop branch build error #3661 — Adjusts the same api-fetch invocation for parse handling in the identical file, using an alternative typing approach.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description only includes the Description section and does not provide the required Motivation and context or How has this been tested sections specified by the repository template.	Please add a Motivation and context section explaining why this change is necessary and a How has this been tested section detailing your testing environment and steps to verify the fix.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly captures the PR’s intent to fix the build error occurring in the develop branch, clearly reflecting the primary objective of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

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

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c02af05 and 96ef772.

⛔ Files ignored due to path filters (8)

• build/admin-settings.asset.php is excluded by !build/**
• build/admin-settings.js is excluded by !build/**
• build/content-helper/dashboard-page.asset.php is excluded by !build/**
• build/content-helper/dashboard-page.js is excluded by !build/**
• build/content-helper/dashboard-widget.asset.php is excluded by !build/**
• build/content-helper/dashboard-widget.js is excluded by !build/**
• build/content-helper/editor-sidebar.asset.php is excluded by !build/**
• build/content-helper/editor-sidebar.js is excluded by !build/**

📒 Files selected for processing (1)

• src/content-helper/common/providers/base-provider.tsx (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*.{js,ts,tsx,jsx}

⚙️ CodeRabbit configuration file

**/*.{js,ts,tsx,jsx}: "Perform a detailed review of the provided code with following key aspects in mind:

• Review the code to ensure it is well-structured and adheres to best practices.
• Verify compliance with WordPress coding standards.
• Ensure the code is well-documented.
• Check for security vulnerabilities and confirm the code is secure.
• Optimize the code for performance, removing any unnecessary elements.
• Validate JSDoc comments for accuracy, currency, and adherence to WordPress coding standards.
• Ensure each line comment concludes with a period.
• Confirm every JSDoc comment includes a @SInCE tag indicating the next version of the plugin to include the code.
• Guarantee compatibility with the latest version of WordPress, avoiding deprecated functions or features."

Files:

• src/content-helper/common/providers/base-provider.tsx

🧬 Code graph analysis (1)

src/content-helper/common/providers/base-provider.tsx (1)

src/content-helper/common/providers/base-wordpress-provider.tsx (1)

• apiFetch (145-189)

⏰ 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: E2E against WordPress latest

🔇 Additional comments (1)

src/content-helper/common/providers/base-provider.tsx (1)

151-151: LGTM! Type-safe approach using spread operator.

The change from type casting to using the spread operator ({ ...options, parse: true }) is a TypeScript best practice. This allows proper type inference while maintaining the same runtime behavior, and correctly fixes the build error by satisfying the type system without suppressing type checks.

---

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.}