Skip to content

Commit

Permalink
remove dead links
Browse files Browse the repository at this point in the history
  • Loading branch information
jnussbaum committed Apr 15, 2024
1 parent 16226bc commit 9e0edd2
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 4 deletions.
3 changes: 1 addition & 2 deletions docs/05-internals/design/api-v2/how-to-add-a-route.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,7 @@ and add code to `ResponderManager` to instantiate the new responder. Then add a
the `receive` method in `ResponderManager`, to match messages that extend your request
message trait, and pass them to that responder's receive method.
The responder's resulting `Future` must be passed to the `ActorUtil.future2Message`.
See [Futures with Pekko](../principles/futures-with-pekko.md) and
[Error Handling](../principles/design-overview.md#error-handling) for details.
See [Error Handling](../principles/design-overview.md#error-handling) for details.

## Write a Route

Expand Down
2 changes: 0 additions & 2 deletions docs/05-internals/design/principles/design-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,8 +94,6 @@ actors. However, the design of reply message passing from actors (by
using `future2Message`), makes sure that any exceptions thrown inside
actors, will reach the route, where they will be handled.

See also [Futures with Akka](futures-with-pekko.md).

## API Routing

The API routes in the `routing` package are defined using the DSL
Expand Down

0 comments on commit 9e0edd2

Please sign in to comment.