mirror of https://github.com/smithy-lang/smithy-rs
Update links (these don't redirect) (#3218)
Fix broken links as a result of repo movement ---- _By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice._
This commit is contained in:
parent
9af2b21e93
commit
8df5ac8545
|
@ -382,7 +382,7 @@ August 1st, 2023
|
|||
}
|
||||
```
|
||||
|
||||
A single `Plugin` can no longer apply a `tower::Layer` on HTTP requests/responses _and_ modelled structures at the same time (see middleware positions [C](https://awslabs.github.io/smithy-rs/design/server/middleware.html#c-operation-specific-http-middleware) and [D](https://awslabs.github.io/smithy-rs/design/server/middleware.html#d-operation-specific-model-middleware). Instead one `Plugin` must be specified for each and passed to the service builder constructor separately:
|
||||
A single `Plugin` can no longer apply a `tower::Layer` on HTTP requests/responses _and_ modelled structures at the same time (see middleware positions [C](https://smithy-lang.github.io/smithy-rs/design/server/middleware.html#c-operation-specific-http-middleware) and [D](https://smithy-lang.github.io/smithy-rs/design/server/middleware.html#d-operation-specific-model-middleware). Instead one `Plugin` must be specified for each and passed to the service builder constructor separately:
|
||||
|
||||
```rust
|
||||
let app = PokemonService::builder_with_plugins(/* HTTP plugins */, /* model plugins */)
|
||||
|
@ -1184,7 +1184,7 @@ September 20th, 2022
|
|||
`aws_smithy_http::operation::Parts` has been renamed to `retry_classifier`.
|
||||
|
||||
**New this release:**
|
||||
- 🎉 (client, [smithy-rs#1647](https://github.com/smithy-lang/smithy-rs/issues/1647), [smithy-rs#1112](https://github.com/smithy-lang/smithy-rs/issues/1112)) Implemented customizable operations per [RFC-0017](https://awslabs.github.io/smithy-rs/design/rfcs/rfc0017_customizable_client_operations.html).
|
||||
- 🎉 (client, [smithy-rs#1647](https://github.com/smithy-lang/smithy-rs/issues/1647), [smithy-rs#1112](https://github.com/smithy-lang/smithy-rs/issues/1112)) Implemented customizable operations per [RFC-0017](https://smithy-lang.github.io/smithy-rs/design/rfcs/rfc0017_customizable_client_operations.html).
|
||||
|
||||
Before this change, modifying operations before sending them required using lower-level APIs:
|
||||
|
||||
|
|
|
@ -4,7 +4,7 @@ Server-side Smithy code generator
|
|||
|
||||
** This is a work in progress and generates serialization/de-serialization code that is probably unusable for the time being. **
|
||||
|
||||
[Design documentation (WIP)](https://awslabs.github.io/smithy-rs/)
|
||||
[Design documentation (WIP)](https://smithy-lang.github.io/smithy-rs/)
|
||||
|
||||
## Project Layout
|
||||
|
||||
|
|
|
@ -38,7 +38,7 @@ Lastly, we emphasize that this RFC does NOT aim to serialize the entire response
|
|||
Users have requested `serde` traits to be implemented on data types implemented in rust SDK.
|
||||
We have created this RFC with the following use cases in mind.
|
||||
1. [[request]: Serialize/Deserialize of models for Lambda events #269](https://github.com/awslabs/aws-sdk-rust/issues/269)
|
||||
2. [Tests](https://awslabs.github.io/smithy-rs/design/faq.html#why-dont-the-sdk-service-crates-implement-serdeserialize-or-serdedeserialize-for-any-types) as suggested in the design FAQ.
|
||||
2. [Tests](https://smithy-lang.github.io/smithy-rs/design/faq.html#why-dont-the-sdk-service-crates-implement-serdeserialize-or-serdedeserialize-for-any-types) as suggested in the design FAQ.
|
||||
3. Building tools
|
||||
|
||||
# Feature Gate
|
||||
|
|
|
@ -14,8 +14,8 @@ These servers, and their clients, are generated using smithy-rs. You're invited
|
|||
to benchmark the performance of these servers to see whether smithy-rs might be
|
||||
a suitable choice for implementing your web service.
|
||||
|
||||
[middleware]: https://awslabs.github.io/smithy-rs/design/server/middleware.html
|
||||
[extractors]: https://awslabs.github.io/smithy-rs/design/server/from_parts.html
|
||||
[middleware]: https://smithy-lang.github.io/smithy-rs/design/server/middleware.html
|
||||
[extractors]: https://smithy-lang.github.io/smithy-rs/design/server/from_parts.html
|
||||
|
||||
|
||||
## Pre-requisites
|
||||
|
|
|
@ -34,7 +34,7 @@
|
|||
//! you absolutely require your middleware to run after deserialization, or to act on particular
|
||||
//! fields of your deserialized operation's input/output/errors.
|
||||
//!
|
||||
//! [the book]: https://awslabs.github.io/smithy-rs/design/server/anatomy.html
|
||||
//! [the book]: https://smithy-lang.github.io/smithy-rs/design/server/anatomy.html
|
||||
//!
|
||||
//! # Filtered application of a HTTP [`Layer`](tower::Layer)
|
||||
//!
|
||||
|
|
Loading…
Reference in New Issue