The Cookie Consent UI should not be part of templates any more. We should, instead, turn the current state into docs for customers to enable, if you wish.
will this mean it's gone from all asp.net core templates? mvc, etc?
Clarified the title. Thanks for the eagle eye @brockallen.
So that's fuckin' awesome -- I can't tell you how many web apps I create from File->New Project and that's the first thing I have to delete. Wahoo!
Removing the cookie-consent is done, now we just have to include it in the docs.
@scottaddie do you need an issue to track the doc changes? I can probably add a section that shows the UI and Middleware if you point me to what doc it should go in
@isaac2004 Yes, please create an issue for this. The following doc would need to be updated for 3.0: https://docs.microsoft.com/en-us/aspnet/core/security/gdpr.
@scottaddie done!
@ryanbrandenburg just realized I forgot to remove Privacy views. Since Cookie consent loads these, should they be removed as well?
The Privacy page is also referenced in the footer (_Layout.cshtml), so we should keep that page.
@ryanbrandenburg FYI docs have been updated as well
Cool, once that PR is merged/approved we can close this out.
@ryanbrandenburg @mkArtakMSFT the doc has been updated
https://github.com/aspnet/AspNetCore.Docs/issues/12720
Thanks @isaac2004!
@ryanbrandenburg looks like nothing else left in here to do. If so, please move this back to Preview7
and close as Done
.
Most helpful comment
So that's fuckin' awesome -- I can't tell you how many web apps I create from File->New Project and that's the first thing I have to delete. Wahoo!