Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/filipw/Strathweb.TypedRouting.AspNetCore
A library enabling strongly typed routing in ASP.NET Core MVC projects.
https://github.com/filipw/Strathweb.TypedRouting.AspNetCore
Last synced: 9 days ago
JSON representation
A library enabling strongly typed routing in ASP.NET Core MVC projects.
- Host: GitHub
- URL: https://github.com/filipw/Strathweb.TypedRouting.AspNetCore
- Owner: filipw
- License: mit
- Created: 2016-05-17T17:21:50.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2019-01-22T19:42:56.000Z (almost 6 years ago)
- Last Synced: 2024-10-15T10:46:49.519Z (21 days ago)
- Language: C#
- Homepage:
- Size: 81.1 KB
- Stars: 75
- Watchers: 5
- Forks: 8
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-dotnet-core - Strathweb.TypedRouting.AspNetCore - A library enabling strongly typed routing in ASP.NET Core MVC projects. (Frameworks, Libraries and Tools / Application Frameworks)
- fucking-awesome-dotnet-core - Strathweb.TypedRouting.AspNetCore - A library enabling strongly typed routing in ASP.NET Core MVC projects. (Frameworks, Libraries and Tools / Application Frameworks)
- awesome-dotnet-core - Strathweb.TypedRouting.AspNetCore - A library enabling strongly typed routing in ASP.NET Core MVC projects. (Frameworks, Libraries and Tools / Application Frameworks)
- awesome-dotnet-core - Strathweb.TypedRouting.AspNetCore - 一个在ASP.NET Core MVC项目中启用强类型路由的库。 (框架, 库和工具 / 应用程序框架)
README
# Strathweb.TypedRouting.AspNetCore
A library enabling strongly typed routing in ASP.NET Core MVC projects.
## Installation
Everything is on [Nuget](https://www.nuget.org/packages/Strathweb.TypedRouting.AspNetCore). [](https://www.nuget.org/packages/Strathweb.TypedRouting.AspNetCore)
```
nuget install Strathweb.TypedRouting.AspNetCore
```
or via the .NET Core CLI:
```
dotnet add package Strathweb.TypedRouting.AspNetCore
```
## Setup
In your `Startup` class, after adding MVC, call `AddTypedRouting();` and then configure your routes:
```csharp
services.AddMvc().AddTypedRouting(opt =>
{
opt.Get("homepage", c => c.Action(x => x.Index()));
opt.Get("aboutpage/{name}", c => c.Action(x => x.About(Param.Any)));
opt.Post("sendcontact", c => c.Action(x => x.Contact()));
});
```
This creates:
* a GET route to `/homepage`
* a GET route to `/aboutpage/{name}`
* a POST route to `/sendcontact`
All of which will route to the relevant methods on our `HomeController`.
## Link generation
Since the API is fluent, you can also give the routes names so that you can use them with i.e. link generation.
```csharp
opt.Get("api/values/{id}", c => c.Action(x => x.Get(Param.Any))).WithName("GetValueById");
```
Now you can use it with `IUrlHelper` (it's a `Url` property on every controller):
```csharp
var link = Url.Link("GetValueById", new { id = 1 });
```
`IUrlHelper` can also be obtained from `HttpContext`, anywhere in the pipeline (i.e. in a filter):
```csharp
var services = context.HttpContext.RequestServices;
var urlHelper = services.GetRequiredService().GetUrlHelper(context);
var link = urlHelper.Link("GetValueById", new { id = 1 });
```
Finally, you can also use this link generation technique with the built-in action results, such as for example `CreatedAtRouteResult`:
```csharp
public IActionResult Post([FromBody]string value)
{
var result = CreatedAtRoute("GetValueById", new { id = 1 }, "foo");
return result;
}
```
## Filters
The route definitions can also be done along with filters that should be executed for a given route. This is equivalent to defining a controller action, and annotating it with a relevant attribute such as action filter or authorization filter.
```csharp
services.AddMvc().AddTypedRouting(opt =>
{
opt.Get("api/items", c => c.Action(x => x.Get())).WithFilters(new AnnotationFilter());
});
```
Filters can also be resolved from ASP.NET Core DI system - as long as they are registered there before.
```csharp
services.AddSingleton();
services.AddMvc().AddTypedRouting(opt =>
{
opt.Get("api/items", c => c.Action(x => x.Get())).WithFilter();
});
```
## Authorization Policies
The route definitions can also have ASP.NET Core authorization policies attached to them.
You can pass in a policy instance:
```csharp
services.AddMvc().AddTypedRouting(opt =>
{
opt.Get("api/secure", c => c.Action(x => x.Foo()).
WithAuthorizationPolicy(new AuthorizationPolicyBuilder().RequireAuthenticatedUser().Build()));
});
```
You can also define a policy as string - then a corresponding policy must be previously registerd in ASP.NET Core DI system.
```csharp
services.AddAuthorization(o =>
{
o.AddPolicy("MyPolicy", b => b.RequireAuthenticatedUser());
});
services.AddMvc().AddTypedRouting(opt =>
{
opt.Get("api/secure", c => c.Action(x => x.Foo()).
WithAuthorizationPolicy("MyPolicy"));
});
```
## Action constraints
The library supports two ways of specifying MVC action constraints:
- inline in the template
- via fluent API
The inline constraints are the same as you can use with attribute routing. For example:
```csharp
opt.Get("api/other/{id:int}", c => c.Action(x => x.Action2(Param.Any)));
```
You can also specify constraints via the fluent API, by chaining `IActionConstraintMetadata` implementations. Consider the following sample constraint class:
```csharp
public class MandatoryHeaderConstraint : IActionConstraint, IActionConstraintMetadata
{
private string _header;
public MandatoryHeaderConstraint(string header)
{
_header = header;
}
public int Order
{
get
{
return 0;
}
}
public bool Accept(ActionConstraintContext context)
{
// only allow route to be hit if the predefined header is present
if (context.RouteContext.HttpContext.Request.Headers.ContainsKey(_header))
{
return true;
}
return false;
}
}
```
You can now use this class in the route declaration:
```csharp
opt.Get("api/other", c => c.Action(x => x.Action1())).WithConstraints(new MandatoryHeaderConstraint("CustomHeader"));
```
## License
[MIT](https://github.com/filipw/Strathweb.TypedRouting.AspNetCore/blob/master/LICENSE)