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

Split out fluent builder generators and clean up #3585

Merged
merged 10 commits into from
Apr 16, 2024

Conversation

jdisanti
Copy link
Collaborator

It looks like I will need to render specialized fluent builders for waiters. This PR is some prerequisite work to split fluent builder generation out of the fluent client generator into its own thing. This makes it possible to refactor the fluent builder generator to be more configurable in a follow up PR so that it can generate waiter fluent builders as well.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jdisanti jdisanti requested a review from a team as a code owner April 13, 2024 00:27
Copy link

A new generated diff is ready to view.

A new doc preview is ready to view.

Co-authored-by: Zelda Hessler <zhessler@amazon.com>
@jdisanti jdisanti enabled auto-merge April 15, 2024 16:53
@jdisanti jdisanti disabled auto-merge April 15, 2024 16:55
Copy link

A new generated diff is ready to view.

A new doc preview is ready to view.

@jdisanti jdisanti requested a review from a team as a code owner April 15, 2024 17:18
Copy link

Copy link

A new generated diff is ready to view.

A new doc preview is ready to view.

@jdisanti jdisanti added this pull request to the merge queue Apr 16, 2024
Merged via the queue into main with commit 94ecd38 Apr 16, 2024
44 checks passed
@jdisanti jdisanti deleted the jdisanti-fluent-builder-cleanup branch April 16, 2024 00:35
Comment on lines +25 to +27
/**
* Generates the client via codegen decorator.
*
Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for explaining the rationale!

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