-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Have one example package per service rather than one per operation #400
Comments
Good point. I'll make the changes soon. |
This was referenced Jun 9, 2021
This is close to being done. Looks like only DynamoDB is left. |
Dynamodb is now also done |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Currently, we have two classes of examples for each service (operation and "hello world"), and each one of these has its own Cargo package, which means with just 8 services, we have 28 example packages with their own Cargo.toml file. It seems like this may not scale in the long run, especially in regards to updating dependencies across the examples.
We should refactor the examples so that there is one example Cargo package per service. So rather than:
We should have just "dynamo", and inside of that, we have different operation and "hello world" examples as separate module files:
The text was updated successfully, but these errors were encountered: