Skip to content

Add support for generating a standalone package #1484

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

Merged
merged 3 commits into from
Jul 1, 2023

Conversation

stof
Copy link
Member

@stof stof commented Jun 30, 2023

This makes the code generator usable outside the async-aws mono-repo by allowing to customize the resolution of the directory corresponding to a given namespace. For standalone packages, we want to write the generated service directly in the root of the repository and the root namespace needs to be configurable (as it won't be an AsyncAws one).

@stof stof force-pushed the out_of_tree_generation branch from 4e85d74 to 4025981 Compare June 30, 2023 12:40
@stof stof mentioned this pull request Jun 30, 2023
@stof stof requested a review from jderusse June 30, 2023 15:23
stof added 3 commits July 1, 2023 14:59
This avoids duplicating the logic in the 2 writers (with slightly
different implementation) and will allow swapping the resolver for
standalone packages.
The generate.php script in the code generator does not make sense as an
executable as it defaults to reading the manifest and generating the
code in the code generator folder itself, which is not the actual use
case.
Configuring it through environment variables also makes it harder to
configure objects like the directory resolver.
This resolver supports the use case of generating a standalone package
containing only one service, where the package is at the root of the
repository.
@stof stof merged commit 18fcf64 into async-aws:master Jul 1, 2023
@stof stof deleted the out_of_tree_generation branch July 1, 2023 15:57
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