Skip to content

Commit

Permalink
Correct outdated details (smithy-lang#2420)
Browse files Browse the repository at this point in the history
  • Loading branch information
jjant authored Feb 28, 2023
1 parent 9f7c49a commit 72df844
Showing 1 changed file with 5 additions and 3 deletions.
8 changes: 5 additions & 3 deletions design/src/server/code_generation.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,15 @@ This document introduces the project and how code is being generated. It is writ

The project is divided in:

- `/codegen`: it contains shared code for both client and server, but only generates a client
- `/codegen-server`: server only. This project started with `codegen` to generate a client, but client and server share common code; that code lives in `codegen`, which `codegen-server` depends on
- `/codegen-core`: contains common code to be used for both client and server code generation
- `/codegen-client`: client code generation. Depends on `codegen-core`
- `/codegen-server`: server code generation. Depends on `codegen-core`
- `/aws`: the AWS Rust SDK, it deals with AWS services specifically. The folder structure reflects the project's, with the `rust-runtime` and the `codegen`
- `/rust-runtime`: the generated client and server crates may depend on crates in this folder. Crates here are not code generated. The only crate that is not published is `inlineable`,
which contains common functions used by other crates, [copied into][2] the source crate

`/rust-runtime` crates ("runtime crates") are added to a crate's dependency only when used. If a model uses event streams, it will depend on [`aws-smithy-eventstream`][3].
Crates in `/rust-runtime` (informally referred to as "runtime crates") are added to a crate's dependency only when used.
For example, if a model uses event streams, the generated crates will depend on [`aws-smithy-eventstream`][3].

## Generating code

Expand Down

0 comments on commit 72df844

Please sign in to comment.