Skip to content
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.

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

🌿 ✨ [Scheduled] Update API Spec #38

Merged
merged 1 commit into from
May 14, 2024
Merged

Conversation

fern-api[bot]
Copy link
Contributor

@fern-api fern-api bot commented May 11, 2024

Summary

Refactored the schema definitions for transformation rules. The TransformReference and TransformFull objects have been replaced with a single TransformRule object.

Added

  • Nothing was added.

Removed

  • The TransformReference and TransformFull objects have been removed.

Changed

  • The TransformRule object now encompasses both reference and full transformation rules, providing a more concise and unified representation.

fern-support added a commit that referenced this pull request May 11, 2024
In favor of automated updates from fern-bot: #38
@dsinghvi dsinghvi requested a review from leggetter May 13, 2024 15:06
@leggetter
Copy link
Collaborator

leggetter commented May 13, 2024

@dsinghvi - what problem does this solve? Or has this been created following a change to the generator?

👀 @alexbouchardd

@leggetter
Copy link
Collaborator

@dsinghvi - so, has the polling action been replaced with something the Fernbot now does? Does it now monitor the API spec?

12cd3c8

@dsinghvi
Copy link
Contributor

@dsinghvi - so, has the polling action been replaced with something the Fernbot now does? Does it now monitor the API spec?

12cd3c8

that's right it does!

@leggetter leggetter merged commit b24284b into main May 14, 2024
1 check passed
@leggetter leggetter deleted the fern/update-api-specs branch May 14, 2024 05:17
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.

2 participants