Skip to content

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Nov 1, 2025

Document settings.disable-explorer-proxy in docs.yml

Summary

Added documentation for the new settings.disable-explorer-proxy configuration option in the docs.yml reference page. This setting allows the API Explorer to bypass the proxy when sending requests directly to the user's API. The documentation includes a warning that Cross-Origin Resource Sharing (CORS) must be enabled on the API when this feature is used.

Changes:

  • Added disable-explorer-proxy: false to the settings configuration example
  • Added ParamField entry with type, default value, and description
  • Included Warning component highlighting the CORS requirement
  • Fixed Vale linting issues (capitalized "API Explorer", defined CORS acronym)

Review & Testing Checklist for Human

  • Verify technical accuracy: Confirm the description "bypass the proxy when sending requests directly to your API" accurately reflects the feature's behavior
  • Assess CORS guidance completeness: Determine if the CORS warning should include specific domains to whitelist (e.g., *.buildwithfern.com, custom domains) or link to setup instructions
  • Preview rendered documentation: Check the preview deployment to verify the new setting appears correctly between disable-search and dark-mode-code and that the Warning component renders properly

Notes

Document the new settings.disable-explorer-proxy option in docs.yml
that allows the API explorer to bypass the proxy when sending requests.
Include a warning about CORS requirements when this feature is enabled.

Co-Authored-By: Catherine Deskur <catherine@buildwithfern.com>
@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

</ParamField>

<ParamField path="settings.disable-explorer-proxy" type="boolean" required={false} default="false" toc={true}>
If set to true, the API explorer will bypass the proxy when sending requests directly to your API.
Copy link
Contributor

Choose a reason for hiding this comment

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

🚫 [vale] reported by reviewdog 🐶
[FernStyles.Reject] Use 'API Explorer' instead of 'API explorer'.

If set to true, the API explorer will bypass the proxy when sending requests directly to your API.

<Warning>
When this feature is enabled, your API must have CORS (Cross-Origin Resource Sharing) enabled to allow requests from the documentation domain.
Copy link
Contributor

Choose a reason for hiding this comment

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

📝 [vale] reported by reviewdog 🐶
[FernStyles.Acronyms] 'CORS' has no definition.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 1, 2025

- Capitalize 'API Explorer' per FernStyles.Reject rule
- Define CORS acronym on first use per FernStyles.Acronyms rule

Co-Authored-By: Catherine Deskur <catherine@buildwithfern.com>
@github-actions
Copy link
Contributor

github-actions bot commented Nov 1, 2025

@chdeskur chdeskur merged commit 5cd96cb into main Nov 2, 2025
2 checks passed
@chdeskur chdeskur deleted the devin/1762013207-document-disable-explorer-proxy branch November 2, 2025 13:36
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.

3 participants