Skip to content

Conversation

@parsapanahpoor
Copy link
Member

@parsapanahpoor parsapanahpoor commented Dec 3, 2025

πŸ“ Description

🎯 Type of Change

  • πŸ› Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • πŸ’₯ Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • πŸ“ Documentation update
  • 🎨 Code style update (formatting, renaming)
  • ♻️ Refactoring (no functional changes)
  • ⚑ Performance improvement
  • βœ… Test update
  • πŸ”§ Build configuration change
  • πŸ”’ Security fix

πŸ”— Related Issues

  • Fixes #
  • Closes #
  • Related to #

πŸ§ͺ Testing

Test Coverage

  • Unit tests added/updated
  • Integration tests added/updated
  • Manual testing performed
  • All existing tests pass

Test Description

Test results:
- [ ] All tests passing
- [ ] No new warnings
- [ ] Code coverage maintained or improved

πŸ“Έ Screenshots / Videos

Screenshots

βœ… Checklist

Code Quality

  • My code follows the project's coding standards
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have removed unnecessary console logs and debugging code
  • My changes generate no new warnings or errors

Documentation

  • I have updated the documentation accordingly
  • I have added/updated XML documentation comments
  • I have updated the README if needed
  • I have updated the CHANGELOG

Testing

  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have tested on multiple browsers/platforms (if applicable)

Breaking Changes

  • This PR introduces breaking changes
  • I have documented all breaking changes in the PR description
  • I have updated the migration guide (if applicable)

πŸ”„ Migration Guide

For users upgrading from previous versions

Before

// Old usage

After

// New usage

πŸ“Š Performance Impact

  • No performance impact
  • Performance improved
  • Performance degraded (explain why this is acceptable)
Performance Benchmarks

πŸ” Additional Context

πŸ“‹ Reviewer Notes


🀝 Contributor Agreement

By submitting this pull request, I confirm that:


Thank you for contributing to JsonViewer.Blazor! πŸŽ‰

@parsapanahpoor parsapanahpoor self-assigned this Dec 3, 2025
@parsapanahpoor parsapanahpoor added the enhancement New feature or request label Dec 3, 2025
@parsapanahpoor parsapanahpoor linked an issue Dec 3, 2025 that may be closed by this pull request
@parsapanahpoor parsapanahpoor moved this from Todo to Done in JsonViewer-Component Dec 3, 2025
@parsapanahpoor parsapanahpoor linked an issue Dec 3, 2025 that may be closed by this pull request
@parsapanahpoor parsapanahpoor merged commit 434eaa4 into main Dec 3, 2025
5 checks passed
@parsapanahpoor parsapanahpoor deleted the 16-feature-release-compatible-version-by-all-net-versions branch December 3, 2025 22:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Development

Successfully merging this pull request may close these issues.

[FEATURE] Release compatible version by all .net versions

2 participants