3d448f7197
This change introduces some new heuristics to make it easier to use 'page' or other resevered parameter names as parameters in URL generation. -- The main change here is to allow the link generation tree to *ignore* a value passed in to URL generation when it conflicts with an endpoint's required values. The main concern of this feature area is "how do we tell whether you are linking to an action or a page?". Routing attempts to do the right thing will requiring very little from the user in terms of expressing intent. In this case, we try to tell the difference between an attempt to generate a link to an action due to the presence of the 'action' parameter and absence of the 'page' parameter. This obviously doesn't work when you want to use 'page' as a non-reserved parameter in an action. The same case occurs for pages, but users are already used to the idea that 'action' is a reserved word in MVC. We can loosen this restriction when the value that's supplied for 'page' is known not to be any existing value of the 'page' route value. This approach seems somewhat reasonable but has many of the problems inherent to this area. When it fails (the value you want to use for 'page' causes a conflict) - it's going to be esoteric and hard to understand. |
||
|---|---|---|
| .. | ||
| Antiforgery | ||
| Azure | ||
| Components | ||
| DataProtection | ||
| DefaultBuilder | ||
| Features/JsonPatch | ||
| Framework | ||
| Hosting | ||
| Html/Abstractions | ||
| Http | ||
| Identity | ||
| Installers | ||
| Middleware | ||
| MusicStore | ||
| Mvc | ||
| ProjectTemplates | ||
| Razor | ||
| Security | ||
| Servers | ||
| Shared | ||
| SignalR | ||
| SiteExtensions | ||
| Tools | ||
| submodules | ||