Skip to content

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Dec 21, 2025

Description

Refs fern-api/fern-platform#6091

Adds support for custom header and footer properties in docs.yml configuration. These properties accept a relative path to a compiled JavaScript file that exports a custom React component to replace the default header or footer in documentation.

Link to Devin run: https://app.devin.ai/sessions/2b482091d11744cfa3111dc19d2f62c2
Requested by: Catherine Deskur (catherine@buildwithfern.com)

Changes Made

  • Updated FDR SDK to version 0.142.21-2bbd2f7e7 which includes the header/footer schema properties
  • Added header and footer optional string properties to DocsConfiguration schema
  • Added header and footer fields to ParsedDocsConfiguration interface
  • Added convertHeaderFooterConfig function in parseDocsConfiguration.ts to resolve file paths and read JS file contents
  • Updated DocsDefinitionResolver.convertDocsConfiguration to include header/footer in the docs shape sent to FDR
  • Added header and footer noop handlers in docs-validator AST visitor
  • Added version 3.31.0 entry to CLI versions.yml

Updates Since Last Revision

  • Rebased from main to incorporate latest changes (versions 3.30.1-3.30.3)
  • Fixed duplicate header/footer property definitions in DocsDefinitionResolver.ts that occurred during merge (removed deprecated undefined placeholders in favor of actual implementation)

Testing

  • Unit tests added/updated
  • Lint checks pass (pnpm run check)
  • Build passes locally (pnpm run fern:build)
  • Biome lint passes

Human Review Checklist

  • Verify the manually added properties in DocsConfiguration.ts won't be overwritten by schema regeneration (file is in schemas/sdk/api/ which suggests it may be auto-generated)
  • Confirm error handling is adequate when the specified JS file doesn't exist (currently readFile will throw)
  • Verify the file contents are correctly passed through to FDR as strings
Add support for custom header and footer React components in documentation.
Users can now specify a relative path to a compiled JavaScript file that
exports a custom React component to replace the default header or footer.

Changes:
- Add header and footer properties to DocsConfiguration schema
- Update ParsedDocsConfiguration interface with header/footer fields
- Update parseDocsConfiguration to read header/footer JS file contents
- Update DocsDefinitionResolver to add header/footer to docs shape
- Update FDR SDK to version 0.142.21-2bbd2f7e7

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
devin-ai-integration bot and others added 3 commits December 21, 2025 01:07
Co-Authored-By: Catherine Deskur <catherine@buildwithfern.com>
Co-Authored-By: Catherine Deskur <catherine@buildwithfern.com>
Co-Authored-By: Catherine Deskur <catherine@buildwithfern.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant