747420e5aa
* [Design] Compatibility switches This introduces a pattern for versioning breaking behaviour changes in minor releases of MVC. The general plan is that application developers choose a release version (2.0, 2.1, Latest) as their baseline which determines the effective 'defaults' for some options. Anything the developer sets explicitly is an override and always wins. Then we add a version setting to the template to point to the current release. This allows us to be progressive with fixing issues and improving areas that don't work well, but offers the developer some choice about when to adopt new behaviours. In effect, we separate new behaviours from the libraries that develiver them. Apps can update the version, and then opt in to new behaviours as a separate change. * Be more american * improve docs, add example * Fix visibility * Fix broken test * Add test * Docs! * The rest of the tests * fix example * Adding docs * PR feedback |
||
|---|---|---|
| .. | ||
| IntegrationTest | ||
| JsonPatchExtensionsTest.cs | ||
| Microsoft.AspNetCore.Mvc.Test.csproj | ||
| MvcOptionsSetupTest.cs | ||
| MvcServiceCollectionExtensionsTest.cs | ||