Skip to content

fix(openapi): Preserve RequestWithoutId and its required fields when bundling #2774

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vdusek merged 1 commit into from
Aug 24, 2026
Merged

fix(openapi): Preserve RequestWithoutId and its required fields when bundling #2774

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions apify-api/openapi/components/schemas/request-queues/Request.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,6 @@ allOf:
- $ref: ./RequestBase.yaml
required:
- id
- uniqueKey
- url
- properties:
id:
$ref: ./SharedProperties.yaml#/RequestId
3 changes: 3 additions & 0 deletions apify-api/openapi/components/schemas/request-queues/RequestBase.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
title: RequestBase
type: object
required:
- uniqueKey
- url
properties:
uniqueKey:
$ref: ./SharedProperties.yaml#/UniqueKey
Expand Down
9 changes: 5 additions & 4 deletions apify-api/openapi/components/schemas/request-queues/RequestWithoutId.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
title: RequestWithoutId
description: A request stored in the request queue, including its metadata and processing state, without the assigned ID.
$ref: ./RequestBase.yaml
required:
- uniqueKey
- url
# Wrapped in a single-member `allOf` so that bundling keeps this component. A bare `$ref` with sibling keys is a

@Pijukatel Pijukatel Aug 24, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Maybe the comment can be just in the description of this PR

# pass-through schema, which the bundler inlines into its target - the component then never reaches the published
# specification, and clients generated from it have no schema for the request-queue write bodies.
allOf:
- $ref: ./RequestBase.yaml
Loading