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

Closed
jdisanti opened this issue May 20, 2021 · 3 comments
Closed

Have one example package per service rather than one per operation #400

jdisanti opened this issue May 20, 2021 · 3 comments

Comments

@jdisanti
Copy link
Collaborator

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:

  • dynamo-add-item
  • dynamo-create-table
  • dynamo-delete-item

We should have just "dynamo", and inside of that, we have different operation and "hello world" examples as separate module files:

  • dynamo
    • add-item.rs
    • create-table.rs
    • delete-item.rs
    • etc...
@Doug-AWS
Copy link
Contributor

Good point. I'll make the changes soon.

@jdisanti
Copy link
Collaborator Author

This is close to being done. Looks like only DynamoDB is left.

@rcoh
Copy link
Collaborator

rcoh commented Aug 30, 2021

Dynamodb is now also done

@rcoh rcoh closed this as completed Aug 30, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants