Try to fix develop build error

[acicovic]

After merging https://github.com/Parsely/wp-parsely/pull/3816 we started getting build errors on develop (see https://github.com/Parsely/wp-parsely/actions/runs/19479384043/job/55747325249). This is a fix attempting to solve the issue.

Summary by CodeRabbit

• Refactor
  • Tightened internal API typing for fetch calls to improve type safety.
  • No changes to behavior, error handling, or user-facing functionality.

[coderabbitai]

📝 Walkthrough

Walkthrough

Cast the options argument to APIFetchOptions<true> when calling apiFetch in the base content-helper provider, tightening the TypeScript typing for the fetch call; no runtime or signature changes.

Changes

Cohort / File(s)	Change Summary
API fetch options casting src/content-helper/common/providers/base-provider.tsx	Cast options to APIFetchOptions<true> when calling apiFetch (e.g., apiFetch<ContentHelperAPIResponse<T>>(options as APIFetchOptions<true>)) to align TypeScript types; no runtime behavior changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Single-file, type-only change.
• Verify the cast is safe and consistent with upstream APIFetchOptions expectations.
• Check related call sites or overloaded apiFetch typings if present.

Possibly related PRs

• Attempt to fix develop branch build error #3661: Fixes the same TypeScript mismatch by casting apiFetch options to APIFetchOptions<true>.
• Fix build error #3731: Adjusts the same apiFetch call with an alternative approach (adding parse: true via spread).

Suggested reviewers

• vaurdan

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description mentions the prior PR and build error link but lacks required template sections: it omits 'Description' of actual changes, 'How has this been tested?', and detailed context beyond the motivation.	Add missing sections: describe the specific type-casting fix in detail, explain the root cause, document testing performed, and link the GitHub Actions error for full context.
Title check	❓ Inconclusive	The title 'Try to fix develop build error' is vague and generic, using imprecise language ('try to fix') that doesn't convey specific technical details about the change.	Replace with a more specific title describing the actual fix, such as 'Fix TypeScript typing in base-provider API call' or 'Correct APIFetchOptions type casting for develop build'.

✅ Passed checks (1 passed)

Check name	Status	Explanation
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 try/fix-develop-build-error

---

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

[coderabbitai]

Actionable comments posted: 1

📜 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 0a3a27e and cfc7165.

📒 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

🧠 Learnings (1)

📓 Common learnings

Learnt from: acicovic
Repo: Parsely/wp-parsely PR: 0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355

Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.

Learnt from: acicovic
Repo: Parsely/wp-parsely PR: 0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355

Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.

Learnt from: acicovic
Repo: Parsely/wp-parsely PR: 2554
File: src/UI/class-settings-page.php:28-29
Timestamp: 2024-10-12T10:01:08.699Z
Learning: acicovic prefers to use the term "resolve" to indicate that an issue or request has been addressed satisfactorily.

Learnt from: acicovic
Repo: Parsely/wp-parsely PR: 2554
File: src/UI/class-settings-page.php:28-29
Timestamp: 2024-06-18T09:33:19.519Z
Learning: acicovic prefers to use the term "resolve" to indicate that an issue or request has been addressed satisfactorily.

🧬 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

[coderabbitai]

Actionable comments posted: 1

📜 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 cfc7165 and bbb65ec.

📒 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

🧠 Learnings (1)

📓 Common learnings

Learnt from: acicovic
Repo: Parsely/wp-parsely PR: 0
File: :0-0
Timestamp: 2024-07-26T21:07:21.167Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355

Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.

Learnt from: acicovic
Repo: Parsely/wp-parsely PR: 0
File: :0-0
Timestamp: 2024-10-16T13:03:58.056Z
Learning: User: acicovic
URL: https://github.com/Parsely/wp-parsely/pull/2355

Timestamp: 2024-04-03T08:04:35.576Z
Learning: In the context of the `wp-parsely` project's documentation, bullet points are consistently capitalized. This standard should be respected in reviews and suggestions regarding document formatting.

Learnt from: acicovic
Repo: Parsely/wp-parsely PR: 2554
File: src/UI/class-settings-page.php:28-29
Timestamp: 2024-06-18T09:33:19.519Z
Learning: acicovic prefers to use the term "resolve" to indicate that an issue or request has been addressed satisfactorily.

Learnt from: acicovic
Repo: Parsely/wp-parsely PR: 2554
File: src/UI/class-settings-page.php:28-29
Timestamp: 2024-10-12T10:01:08.699Z
Learning: acicovic prefers to use the term "resolve" to indicate that an issue or request has been addressed satisfactorily.

🧬 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