Conversation
- Removed "classic" and "modern" styles in favor of just one single style. - Introduced `standalone.style.css` for independent themes without dependencies on `common.css` or `ui.js`. - Enhanced maintainability by restructuring CSS files and removing unused styles.
- Removed "modern." prefixes from CSS/JS filenames for simplicity. - Consolidated `Style` and `ModernStyle` into a single `Theme` class. - Renamed all "Style" references to "Theme" across the codebase. - Added support for standalone themes (no `common.css` or `ui.js`). - Updated `FileProvider.cs` to handle themes and standalone logic. - Refactored `SwaggerUIBuilderExtensions` and `NSwagBuilderExtensions`. - Updated tests, samples, and documentation to reflect changes. - Removed classic styles and related logic (breaking change).
Revised README.md and package-readme.md to improve clarity, structure, and visual appeal. Added new sections for quick start, features, and breaking changes. Updated badges, links, and examples for Swashbuckle and NSwag. Adjusted NuGet.props to fix `PackagePath` for `package-readme.md`. Updated readme.txt with detailed release notes for v3.0.0, highlighting breaking changes, .NET 10 support, and other improvements. Enhanced user guidance with links to migration guides and documentation.
…re in project files
Introduced a theme switcher feature enabling users to dynamically switch between predefined and custom themes in Swagger UI. Added support for predefined themes and custom themes. Enhanced `Program.cs` with examples of using themes and advanced options. Updated `FileProvider.cs` to expose theme metadata as a JSON endpoint for the theme switcher. Refactored `BaseTheme.cs` for better theme name handling. Updated CSS and JavaScript files to support the theme switcher, including dropdown styles and runtime switching logic. Added new CSS files for predefined and custom themes. Improved caching, resource management, and advanced UI features in `AdvancedOptions.cs` and `FileProvider.cs`. Enhanced testing coverage with `ThemeSwitcherTests`, `FileProviderMiddlewareTests`, and updates to `ThemeProviderTests`. Improved documentation, comments, and ensured backward compatibility with existing configurations.
- Support organizing themes in subfolders (SwaggerThemes.CompanyThemes.*, etc.) - Fix exact filename matching: "custom.css" no longer matches "standalone.custom.css" - Add comprehensive tests with real duplicate files
Updated CONTRIBUTING.md to enhance readability and organization: - Reworded "How to Contribute" steps for better emphasis. - Added a "Project Structure" section to explain the codebase layout. - Enhanced "Working with Themes" with clearer minification steps. - Introduced a "Testing Your Changes" section with detailed instructions. - Improved "Pull Request Guidelines" with best practices for PRs. - Expanded "Reporting Bugs" and "Suggesting Features" sections. - Added a "Development Tips" section for rapid iteration and theme organization. - Clarified licensing terms and added a friendly closing note. - Updated contributor credit with a link to @teociaps' GitHub profile.
…igurer - Downgraded `Swashbuckle.AspNetCore` to version `9.0.6` (v10 as dependency has to many breaking changes). - Upgraded `NSwag.AspNetCore` to latest.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduced a theme switcher feature enabling users to dynamically switch between predefined and custom themes in Swagger UI. Added support for predefined themes and custom themes.
In addition, this pull request makes significant improvements to project documentation, contribution guidelines, and code of conduct, as well as minor build configuration updates. The most impactful changes are comprehensive rewrites and enhancements to
README.mdandCONTRIBUTING.mdto better guide users and contributors, an updated and clarified code of conduct, and minor fixes for build and packaging.Documentation and Community Improvements:
Major rewrite and modernization of
README.md:Substantial overhaul of
CONTRIBUTING.md:Updated and expanded
CODE_OF_CONDUCT.md:Build and Packaging Adjustments:
SwaggerUI.Themes.slnfor Visual Studio 18 compatibility.build/Common.Core.props.package-readme.mdinbuild/NuGet.props.