aa90efa5b7
* Fixing a few nullable reference types for log viewer (#13634) (cherry picked from commitb4ca2a6636) * Adding LogControllerBase * Migrating GetLogLevels() * Migrating GetNumberOfErrors() * Migrating GetLogLevelCounts() * Migrating GetCanViewLogs() * Migrating GetMessageTemplates() * Migrating GetLogs() * Migrating GetSavedSearches() * Migrating PostSavedSearch() * Migrating DeleteSavedSearch() * Adding LoggerViewModel * Adding LogViewModelMapDefinition * Update OpenApi.json * Cleanup * V12: Change nullability for the log searches (#13647) * Changing nullability * Obsolete DeleteSavedSearch since the query param is not used * Fix a bit more referenced * Add default implementation for the new overload of DeleteSavedSearch (cherry picked from commit5e06f5a8a0) * Updates based on nullability fix * Adding GetSavedSearchByName * Implementing ByName endpoint * Refactoring Delete endpoint based on GetSavedSearchByName * Refactoring Create endpoint to return the item's location * Suppress new GetSavedSearchByName in ILogViewer interfaces * Update OpenApi.json * Adding github initials to FIXME * Renaming * Moving files to Core proj * Adding GetLogs with skip and take * Introducing ILogViewerService * Supressing xml for ILogViewer.GetLogsAsPagedModel() * Changing to our own Enum representation of LogLevel * Creating ILogEntry needed for GetPagedLogs() * Refactoring controllers to use the new logViewerService * Removing base class methods since those have been moved to the new service * Removing ErrorCountLogViewerController since the result can be calculated from another endpoint * Refactoring the MapDefinition because of the new return types from the service * Update OpenApi.json * Obsoleting old methods in favor of the ILogViewerService * Cleanup * Fixing enum representation as strings for Swagger * Adding documentation * Changing enum representation to string in OpenApi.OpenApi.json * Fix FIXME (use CreatedAtAction) * Removing JsonStringEnumConverter as there should be another way to fix enum representation for Swagger * Removing MappingBuilderExtensions and making specific LogViewerBuilderExtensions * Changes to the .sln file * Take only the result in the response * Register the LogViewer extensions * Update OpenApi.json * Fix the supressions.xml * Add inheritdoc * Remove GetSavedSearchByName as it isn't necessary to introduce it anymore * Obsolete interfaces * Rename ViewPermission controller to ValidateLogFileSize * Make rest of the methods async * Route name change * Remove methods obsoletion * Introduce the "attempt" pattern * Refactoring of ILogViewerService * Refactoring controllers * Another OpenApi.json update * Adding fixme * Re-add new client project Co-authored-by: nikolajlauridsen <nikolajlauridsen@protonmail.ch>
Umbraco CMS · 
Umbraco is the friendliest, most flexible and fastest growing ASP.NET CMS, and used by more than 500,000 websites worldwide. Our mission is to help you deliver delightful digital experiences by making Umbraco friendly, simpler and social.
Learn more at umbraco.com
See the official Umbraco website for an introduction, core mission and values of the product and team behind it.
Please also see our Code of Conduct.
Getting Started
Umbraco Cloud is the easiest and fastest way to use Umbraco yet, with full support for all your custom .NET code and integrations. You're up and running in less than a minute, and your life will be made easier with automated upgrades and a built-in deployment engine. We offer a free 14-day trial, no credit card needed.
If you want to DIY, then you can download Umbraco either as a ZIP file or via NuGet. It's the same version of Umbraco CMS that powers Umbraco Cloud, but you'll need to find a place to host it yourself, and handling deployments and upgrades will be all up to you.
Documentation
The documentation for Umbraco CMS can be found on Our Umbraco. The source for the Umbraco docs is open source as well and we're happy to look at your documentation contributions.
Join the Umbraco community
Our friendly community is available 24/7 at the community hub, we call "Our Umbraco". Our Umbraco features forums for questions and answers, documentation, downloadable plugins for Umbraco, and a rich collection of community resources.
Besides "Our", we all support each other in our Community Discord Server and on Twitter: Umbraco HQ, Release Updates, #umbraco
Contributing
Umbraco is contribution-focused and community-driven. If you want to contribute back to the Umbraco source code, please check out our guide to contributing.