Rask.Api
0.20.1-alpha.0.228
dotnet add package Rask.Api --version 0.20.1-alpha.0.228
NuGet\Install-Package Rask.Api -Version 0.20.1-alpha.0.228
<PackageReference Include="Rask.Api" Version="0.20.1-alpha.0.228" />
<PackageVersion Include="Rask.Api" Version="0.20.1-alpha.0.228" />
<PackageReference Include="Rask.Api" />
paket add Rask.Api --version 0.20.1-alpha.0.228
#r "nuget: Rask.Api, 0.20.1-alpha.0.228"
#:package Rask.Api@0.20.1-alpha.0.228
#addin nuget:?package=Rask.Api&version=0.20.1-alpha.0.228&prerelease
#tool nuget:?package=Rask.Api&version=0.20.1-alpha.0.228&prerelease
Rask.Api
Ordinary ASP.NET Core API controllers and minimal API endpoints, hosted properly inside a Rask app.
builder.Services.AddRaskApi();
...
app.MapRaskApi();
app.UseRask<App>();
Write the endpoint however you normally would — an [ApiController] class, or app.MapGet(...). Nothing
about it is Rask-specific.
What this actually fixes
Not ordering. Endpoint routing matches on precedence, never on registration order, and every route
you write is more specific than Rask's /{**path} catch-all — so your endpoints answer from either side
of UseRask, and always did.
What order cannot fix is a request under your API prefix matching nothing. Without a guard it
reaches the catch-all and renders the app, so a mistyped or deleted route answers 200 with a web page,
and the caller's JSON parse fails somewhere a long way from the cause. MapRaskApi() answers 404 with
an RFC 9457 problem document under ApiOptions.Prefix (default /api) and leaves every other path alone.
It is an ordinary endpoint rather than a fallback on purpose: a fallback sits at int.MaxValue and would
lose to the catch-all, while at the same order /api/{**rest} outranks /{**path} — and loses in turn to
every real route beneath it.
The typed client
Rask.Api.Client generates a typed client from these same endpoints, so browser and component code calls
await posts.Get(3) instead of writing the URL, the verb and the response type out by hand a second time.
Documentation: https://rask.sh
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- No dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Rask.Api:
| Package | Downloads |
|---|---|
|
Rask
The one reference a Rask application needs, server or browser. On net10.0 it brings the ASP.NET host plus every battery — database, mediator, background jobs, transactional email, cache, outbox, operator dashboard, durable logs, Web Push, and SQLite snapshots and continuous backup — with RaskApp.Create(args) as the entry point. On net10.0-browser it brings the WebAssembly host, the source-generated mediator, the query cache and remote dispatch. Everything referenced is wired and on; app.Configure(c => c.Jobs.Off()) is how an app does without one. Reference Rask.Server for a lean host with no database. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.20.1-alpha.0.228 | 35 | 9/4/2026 |
| 0.20.1-alpha.0.227 | 28 | 9/4/2026 |
| 0.20.1-alpha.0.226 | 37 | 9/4/2026 |
| 0.20.1-alpha.0.225 | 39 | 9/4/2026 |
| 0.20.1-alpha.0.224 | 36 | 9/4/2026 |
| 0.20.1-alpha.0.223 | 40 | 9/4/2026 |
| 0.20.1-alpha.0.221 | 42 | 9/4/2026 |
| 0.20.1-alpha.0.220 | 38 | 9/4/2026 |
| 0.20.1-alpha.0.217 | 46 | 9/4/2026 |
| 0.20.1-alpha.0.216 | 40 | 9/4/2026 |
| 0.20.1-alpha.0.215 | 43 | 9/3/2026 |
| 0.20.1-alpha.0.213 | 40 | 9/3/2026 |
| 0.20.1-alpha.0.212 | 39 | 9/3/2026 |