RouteConcatenation

All Known Subinterfaces:

Directives

All Known Implementing Classes:

Directives$, HttpApp, RouteConcatenation$
```
public interface RouteConcatenation
```

Nested Class Summary

Nested Classes
Modifier and Type Interface Description

static class RouteConcatenation.RouteWithConcatenation

Method Summary

All Methods Instance Methods Abstract Methods
Modifier and Type	Method	Description
`RouteConcatenation.RouteWithConcatenation`	`_enhanceRouteWithConcatenation(scala.Function1<RequestContext,scala.concurrent.Future<RouteResult>> route)`
`scala.Function1<RequestContext,scala.concurrent.Future<RouteResult>>`	`concat(scala.collection.immutable.Seq<scala.Function1<RequestContext,scala.concurrent.Future<RouteResult>>> routes)`	Tries the supplied routes in sequence, returning the result of the first route that doesn't reject the request.

- Method Detail
  - _enhanceRouteWithConcatenation
```
RouteConcatenation.RouteWithConcatenation _enhanceRouteWithConcatenation(scala.Function1<RequestContext,scala.concurrent.Future<RouteResult>> route)
```
    Parameters:
    
    route - (undocumented)
    
    Returns:
    
    (undocumented)
  - concat
```
scala.Function1<RequestContext,scala.concurrent.Future<RouteResult>> concat(scala.collection.immutable.Seq<scala.Function1<RequestContext,scala.concurrent.Future<RouteResult>>> routes)
```
    Tries the supplied routes in sequence, returning the result of the first route that doesn't reject the request. This is an alternative to direct usage of the infix ~ operator. The ~ can be prone to programmer error, because if it is omitted, the program will still be syntactically correct, but will not actually attempt to match multiple routes, as intended.
    
    Parameters:
    
    routes - subroutes to concatenate
    
    Returns:
    
    the concatenated route