feat(cli): allow absolute API spec paths in generators.yml#16063
feat(cli): allow absolute API spec paths in generators.yml#16063FedeZara wants to merge 1 commit into
Conversation
Resolve absolute OpenAPI, GraphQL, OpenRPC, and protobuf paths (plus overrides and overlays) at workspace load time and propagate them through loading, validation, generation, and fern api update. Co-authored-by: Cursor <cursoragent@cursor.com>
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.
Tip: disable this comment in your organization's Code Review settings.
Docs Generation Benchmark ResultsComparing PR branch against median of 5 nightly run(s) on
Docs generation runs |
SDK Generation Benchmark ResultsComparing PR branch against median of 5 nightly run(s) on Full benchmark table (click to expand)
main (generator): generator-only time via --skip-scripts (includes Docker image build, container startup, IR parsing, and code generation — this is the same Docker-based flow customers use via |
Summary
generators.ymlfor OpenAPI, GraphQL, OpenRPC, and protobuf specs, plus overrides and overlays.@fern-api/fs-utilsand propagate resolved paths through workspace loading, OSS validation, generation prep, andfern api update.Context
This is the feature follow-up to #15953, which intentionally rejects absolute OpenAPI paths with a user-facing config error to fix Sentry CLI-18 / CLI-46 without changing supported configuration semantics yet.
Linear: https://linear.app/buildwithfern/issue/FER-10741/allow-absolute-api-spec-paths-in-generatorsyml
Test plan
pnpm turbo run test --filter @fern-api/fs-utils --filter @fern-api/workspace-loader --filter @fern-api/lazy-fern-workspace --filter @fern-api/oss-validator --filter @fern-api/cligenerators.ymlwith absolute OpenAPI path loads andfern generate --localsucceeds when the file exists locally