Merge pull request #515 from TimeWarpEngineering/Cramer/2024-12-05/Samples

11.0.0 Release version

Author: StevenTCramer

Directory.Build.props

@@ -1,7 +1,7 @@
 <Project>
   <!-- Set common properties regarding assembly information and nuget packages -->
   <PropertyGroup>
-    <TimeWarpStateVersion>11.0.0-beta.96+8.0.403</TimeWarpStateVersion>
+    <TimeWarpStateVersion>11.0.0</TimeWarpStateVersion>
     <Authors>Steven T. Cramer</Authors>
     <Product>TimeWarp State</Product>
     <PackageVersion>$(TimeWarpStateVersion)</PackageVersion>

Documentation/Blips/2024-02-TimeWarp-State-11-Release.md

@@ -0,0 +1,14 @@
+# TimeWarp.State 11.0.0 Release
+
+🚀 Announcing TimeWarp.State 11.0.0!
+
+Blazor-State has evolved into TimeWarp.State, bringing powerful new features for #Blazor state management:
+
+✨ New TimeWarp.State.Plus package
+🛡️ Architecture enforcement with TimeWarp.State.Policies
+⚡ Enhanced performance & developer tools
+🎯 Targeting .NET 8
+
+Learn more: [Blog Post Link]
+
+#dotnet #blazor #webdev #opensource

Documentation/Blips/Index.md

@@ -0,0 +1,34 @@
+# Blips
+
+## What Are Blips?
+
+Blips are short-form, public posts designed to be concise and impactful. They serve as quick messages or updates that can be pushed to various social media platforms. In this repository, Blips are crafted and stored for use, with the initial focus on platforms like **X** and **NOSTR**.
+
+## Purpose
+
+This repository's Blips folder acts as a centralized location for creating, reviewing, and managing content intended for social media distribution. By organizing Blips in a structured way, it ensures consistency, reusability, and efficiency when posting to multiple platforms.
+
+## Key Features of Blips
+
+1. **Concise Communication**: Each Blip is short, focused, and to the point.
+2. **Multi-Platform Ready**: While initially targeting **X** and **NOSTR**, the format is adaptable for other platforms like BlueSky and Threads in the future.
+3. **Centralized Management**: All Blips are stored here for tracking and collaboration.
+
+## Workflow
+
+1. **Creation**: Write Blips in Markdown for clarity and simplicity.
+2. **Review**: Ensure the message aligns with the intended tone, platform guidelines, and audience.
+3. **Publishing**: Push the Blip to social media platforms using the appropriate tools or integrations.
+
+## Future Plans
+
+As this system evolves:
+- Additional platforms may be supported.
+- Automation tools may be implemented for seamless posting.
+- Analytics might be incorporated to track engagement and refine Blip strategies.
+
+## Related Topics
+
+- Guidelines for Writing Effective Blips
+- Pushing Blips to **X** and **NOSTR**
+- Expanding to Other Platforms

Documentation/Blogs/2024-02-TimeWarp-State-11-Release.md

@@ -0,0 +1,55 @@
+# TimeWarp.State 11.0.0: A New Era in Blazor State Management
+
+We're thrilled to announce the release of TimeWarp.State 11.0.0, marking a significant milestone in our journey. Previously known as Blazor-State, this release represents not just a rebranding but a major evolution in state management for Blazor applications.
+
+## What's New in TimeWarp.State?
+
+### 🚀 Major Enhancements
+
+#### TimeWarp.State.Plus Package
+We've introduced a new package packed with advanced features:
+- **Timer System**: Robust timer management with MultiTimer support and activity-based reset capabilities
+- **Enhanced Routing**: New TwBreadcrumb and TwPageTitle components
+- **Improved Caching**: TimeWarpCacheableState for better state persistence
+
+#### TimeWarp.State.Policies Package
+Enforce architectural patterns with our new policies package:
+- BeNestedInStateCustomRule for proper nesting
+- HaveInjectableConstructor rule
+- HaveJsonConstructor rule
+- Comprehensive Action, ActionHandler, ActionSet, and State policies
+
+### 💡 Key Features
+
+- **Flexible State Inheritance**: Chain inherits from State<> to create custom BaseState<> implementations
+- **ActionSet Source Generator**: Simplified action creation
+- **Persistent State**: New [PersistentState] attribute for state persistence
+- **Enhanced Action Tracking**: Improved capabilities with ActionTrackingState
+- **Advanced Rendering Control**: Fine-grained control over component re-rendering through TimeWarpStateComponent
+- **Better Performance**: New RenderMode and RenderReasons tracking for optimized rendering
+
+### 🛠 Developer Experience
+
+- **Improved Analyzers**: TimeWarp.State.Analyzer provides comprehensive code analysis
+- **Enhanced Source Generators**: Improved development productivity
+- **Comprehensive Samples**: New examples demonstrating various features:
+  - Basic State and Action Handler usage
+  - Redux DevTools integration
+  - Action Tracking capabilities
+  - Advanced routing features
+
+## Breaking Changes
+
+TimeWarp.State 11.0.0 requires .NET 8.0 or later. The rebranding means you'll need to update:
+- Package references from `Blazor-State` to `TimeWarp.State`
+- Namespace references from `BlazorState` to `TimeWarp.State`
+
+For detailed migration instructions, check our [Migration Guide](xref:BlazorState:Migration10-11.md).
+
+## Looking Forward
+
+This release sets a new foundation for state management in Blazor applications. With improved performance, enhanced developer tools, and new features, TimeWarp.State 11.0.0 provides a robust solution for managing application state.
+
+We're committed to continuing this evolution, making state management in Blazor applications more powerful and developer-friendly.
+
+Ready to get started? Check out our [documentation](https://timewarpengineering.github.io/timewarp-state/) for comprehensive guides and examples.

Kanban/ToDo/014-Validate-Program-Main-Usage-In-Samples.md Kanban/Done/014-Validate-Program-Main-Usage-In-Samples.md

@@ -26,40 +26,40 @@ Create a comprehensive tutorial that guides users through building Sample03Wasm,
 ## Checklist
 
 ### Design
-- [ ] Review Sample01Wasm (ReduxDevTools) implementation
-- [ ] Review Sample03Wasm routing implementation
-- [ ] Map progression path from ReduxDevTools to routing features
-- [ ] Identify key learning points and concepts
+- [x] Review Sample01Wasm (ReduxDevTools) implementation
+- [x] Review Sample03Wasm routing implementation
+- [x] Map progression path from ReduxDevTools to routing features
+- [x] Identify key learning points and concepts
 
 ### Implementation
-- [ ] Create step-by-step tutorial structure
-- [ ] Document initial setup from ReduxDevTools base
-- [ ] Detail routing feature implementation steps
-- [ ] Include code samples for each routing action
-- [ ] Add configuration and integration steps
-- [ ] Include thread safety implementation details
-- [ ] Document ReduxDevTools integration for route debugging
+- [x] Create step-by-step tutorial structure
+- [x] Document initial setup from ReduxDevTools base
+- [x] Detail routing feature implementation steps
+- [x] Include code samples for each routing action
+- [x] Add configuration and integration steps
+- [x] Include thread safety implementation details
+- [x] Document ReduxDevTools integration for route debugging
 
 ### Documentation
-- [ ] Add tutorial to Documentation/Tutorial folder
-- [ ] Include screenshots of:
+- [x] Add tutorial to Documentation/Tutorial folder
+- [x] Include screenshots of:
   * Route state in ReduxDevTools
   * Breadcrumb navigation
   * Navigation stack visualization
-- [ ] Add diagrams explaining:
+- [x] Add diagrams explaining:
   * Stack-based navigation flow
   * Route state management
-- [ ] Include troubleshooting section
-- [ ] Add best practices section
-- [ ] Cross-reference with existing tutorials
+- [x] Include troubleshooting section
+- [x] Add best practices section
+- [x] Cross-reference with existing tutorials
 
 ### Review
-- [ ] Verify tutorial progression logic
-- [ ] Test all code samples
-- [ ] Validate ReduxDevTools integration steps
-- [ ] Review thread safety explanations
-- [ ] Check clarity of routing concepts
-- [ ] Ensure consistency with existing documentation
+- [x] Verify tutorial progression logic
+- [x] Test all code samples
+- [x] Validate ReduxDevTools integration steps
+- [x] Review thread safety explanations
+- [x] Check clarity of routing concepts
+- [x] Ensure consistency with existing documentation
 
 ## Notes
 

Kanban/ToDo/016-Create-Sample03Wasm-Tutorial.md Kanban/Done/016-Create-Sample03Wasm-Tutorial.md

@@ -0,0 +1,134 @@
+# Task 017: Push To Production
+
+## Description
+
+Prepare TimeWarp.State for production release by updating version numbers, removing prerelease flags, and ensuring all production readiness requirements are met.
+
+## Requirements
+
+- Update version in Directory.Build.props from 11.0.0-beta.96+8.0.403 to 11.0.0
+- Remove --prerelease flags from all sample project package references
+- Ensure all documentation is up to date
+- Verify all samples are working with production version
+- Update release notes
+
+## Summary of Blocking Issues
+
+1. Critical Issues (New Tasks Created):
+   - Task 018: Fix Sample03-Routing state persistence issue (state resets during navigation)
+   - Task 019: Fix Sample00-StateActionHandler Auto project structure
+   - Task 020: Fix 36 documentation warnings for invalid links and cross-references
+
+2. Path to Production:
+   - Complete Tasks 018, 019, and 020
+   - Re-verify all samples with fixes applied
+   - Final review of documentation with all warnings resolved
+   - Conduct final security and performance review
+   - Test package installation in a new project
+   - Release to production
+
+## Checklist
+
+### Design
+- [x] Review current version number and update plan
+- [x] Review all sample projects for prerelease dependencies
+
+### Implementation
+- [x] Update TimeWarpStateVersion in Directory.Build.props to 11.0.0
+- [x] Remove --prerelease flags from all sample project package references:
+  - [x] Sample00-StateActionHandler
+  - [x] Sample01-ReduxDevTools
+  - [x] Sample02-ActionTracking
+  - [x] Sample03-Routing
+- [x] Update package versions in all sample project files to 11.0.0
+- [ ] Run all samples to verify they work with production version
+  - [x] Sample00-StateActionHandler Server (Verified working)
+  - [x] Sample00-StateActionHandler Wasm (Verified working)
+  - [x] Sample01-ReduxDevTools (Verified working - base functionality works, Redux DevTools warning expected)
+  - [x] Sample02-ActionTracking (Verified working - action tracking functionality fully operational)
+  - [x] Sample03-Routing (Partial - routing works but state persistence issue found, see Task 018)
+  - [ ] Sample00-StateActionHandler Auto (Needs investigation - project structure issue, see Task 019)
+- [x] Update packages.lock.json files
+- [x] Run all tests to ensure everything passes
+- [x] Build and verify NuGet packages
+
+### Documentation
+- [x] Update Release Notes for 11.0.0
+- [x] Review and update main documentation
+- [x] Update sample documentation to remove prerelease references
+- [x] Verify documentation build and deployment (Build succeeds with warnings, see Task 020)
+- [x] Update README.md if needed (No updates required)
+
+### Review
+- [x] Review all breaking changes
+- [ ] Verify all features are production-ready (Pending completion of Tasks 018, 019)
+- [ ] Check for any deprecated features or warnings
+- [ ] Review performance metrics
+- [ ] Review security implications
+- [ ] Conduct final code review
+- [ ] Test package installation in a new project
+
+## Notes
+
+- This release marks the transition from beta to production for version 11.0.0
+- All samples should be updated to use the production version
+- Documentation should reflect production status
+- Consider creating a release checklist template for future releases
+- Sample00-StateActionHandler Auto needs investigation for project structure issues (Task 019)
+- Sample03-Routing state persistence issue needs investigation before production release (Task 018)
+- Documentation warnings need to be resolved (Task 020)
+- All test suites passing with expected skipped tests:
+  - TimeWarp.State.Analyzer.Tests: 4 passed
+  - TimeWarp.State.Tests: 16 passed, 1 skipped
+  - TimeWarp.State.Plus.Tests: 8 passed, 1 skipped
+  - Client.Integration.Tests: 11 passed, 1 skipped
+  - Test.App.Architecture.Tests: 7 passed, 1 skipped
+
+## Implementation Notes
+
+- Updated Directory.Build.props version to 11.0.0
+- Removed --prerelease flags from Sample00-StateActionHandler documentation (both Server and Auto)
+- Verified no other samples contained prerelease flags
+- Reviewed Release11.0.0.md and confirmed it's comprehensive and up-to-date
+- Searched all documentation for any remaining beta/prerelease references and found none
+- Updated package versions to 11.0.0 in all sample projects:
+  - Sample00-StateActionHandler (Server, Wasm, Auto)
+  - Sample01-ReduxDevTools
+  - Sample02-ActionTracking
+  - Sample03-Routing
+  - Updated both TimeWarp.State and TimeWarp.State.Plus where applicable
+- Built and published NuGet packages version 11.0.0 to local feed
+- Verified Sample00-StateActionHandler Server working with production version
+- Noted issue with Sample00-StateActionHandler Auto project structure - created Task 019
+- Verified Sample00-StateActionHandler Wasm working with production version - counter functionality working as expected
+- Verified Sample01-ReduxDevTools working with production version:
+  - Base counter functionality working correctly
+  - Redux DevTools integration properly warns when DevTools not installed (expected behavior)
+- Verified Sample02-ActionTracking working with production version:
+  - Counter functionality working correctly
+  - Action tracking state updates properly
+  - Both 2-second and 5-second actions work as expected
+  - Active action status displayed correctly
+- Tested Sample03-Routing with production version:
+  - Basic routing functionality works (navigation and breadcrumbs)
+  - Page titles update correctly
+  - Issue found: State does not persist when navigating between pages - created Task 018
+  - Counter resets to 0 after navigation, should maintain previous value
+- Ran all test suites successfully:
+  - All core functionality tests passing
+  - Architecture tests passing
+  - Integration tests passing
+  - Only expected example tests skipped
+- Documentation build completed with warnings - created Task 020:
+  - Documentation compiles successfully
+  - 36 warnings found, mostly related to file links and cross-references
+  - No critical errors that would prevent documentation deployment
+- README.md reviewed and confirmed up-to-date:
+  - Version references correct
+  - Installation instructions accurate
+  - Documentation links valid
+  - No prerelease content present
+- Created new tasks for blocking issues:
+  - Task 018: Fix Routing State Persistence
+  - Task 019: Fix Auto Sample Project Structure
+  - Task 020: Fix Documentation Warnings

Kanban/Done/017-Push-To-Production.md

@@ -0,0 +1,45 @@
+# Task 018: Fix Routing State Persistence
+
+## Description
+
+Fix state persistence issue in Sample03-Routing where state resets when navigating between pages. Currently, the counter value resets to 0 after navigation when it should maintain its previous value.
+
+## Requirements
+
+- Investigate why state is not persisting during navigation
+- Fix state persistence in Sample03-Routing
+- Ensure counter value maintains its value across page navigation
+- Update any relevant documentation
+
+## Checklist
+
+### Design
+- [ ] Review current routing implementation
+- [ ] Analyze state management during navigation
+- [ ] Design solution for state persistence
+
+### Implementation
+- [ ] Fix state persistence issue
+- [ ] Add tests to verify state persistence across navigation
+- [ ] Update sample documentation if needed
+
+### Testing
+- [ ] Verify counter state persists after navigation
+- [ ] Test other state values persist correctly
+- [ ] Run all tests to ensure no regressions
+
+### Documentation
+- [ ] Update any relevant documentation
+- [ ] Add notes about state persistence in routing documentation
+- [ ] Update sample comments if needed
+
+## Notes
+
+- Issue discovered during production release preparation
+- Counter resets to 0 when navigating away and back
+- Should maintain state across navigation
+- Part of production readiness requirements
+
+## Implementation Notes
+
+- Add implementation notes as the task progresses