feat: Add Development Tools section to Event Store#2791
Conversation
- Introduced a new Development Tools component for managing event store states. - Added functionality to reset all states and individual event stores. - Updated routing to include Development Tools in the Event Store menu. - Enhanced localization with new strings for Development Tools. - Marked several API classes to treat warnings as errors for better validation.
|
@copilot fix all ci issues |
…mentTools and integration tests Co-authored-by: woksin <13407188+woksin@users.noreply.github.com>
…ation test Co-authored-by: woksin <13407188+woksin@users.noreply.github.com>
…Docker with DEVELOPMENT, fix test pollution Co-authored-by: woksin <13407188+woksin@users.noreply.github.com>
Co-authored-by: woksin <13407188+woksin@users.noreply.github.com>
…ker image build Co-authored-by: woksin <13407188+woksin@users.noreply.github.com>
Co-authored-by: woksin <13407188+woksin@users.noreply.github.com>
…em event store, remove unused using Co-authored-by: woksin <13407188+woksin@users.noreply.github.com>
…reserve auth state Co-authored-by: woksin <13407188+woksin@users.noreply.github.com>
…ertions into single fact Co-authored-by: woksin <13407188+woksin@users.noreply.github.com>
|
@woksin Great, I love the idea of being able to just «reset». On a reset, we should rerun any seed data. A second note; we have at the top of the React hierarchy the You could even toggle it specifically in the |
…oolean, remove IActionResult, and adjust event store reset logic
Fix CI: restore generated proxies, fix specs, and fix integration test failures
…eConnection and related components
- Added `ClientConnectionManager` to manage client connections, including registration, unregistration, and disconnection of all clients. - Introduced logging for connection management actions. - Created unit tests for connection management functionalities, including connection registration, unregistration, and disconnection scenarios. - Developed `ConnectionService` to handle client connection requests and keep-alive pings, ensuring proper interaction with the `ClientConnectionManager`. - Implemented development tools for resetting all state and event stores, with appropriate blocking of connections during these operations. - Removed obsolete API files related to development tools. - Updated the front-end to conditionally render development tools based on the environment.
|
@einari wanna have a second look here? |
Summary
Adds development-only reset tooling for Chronicle, including backend endpoints, reset-aware connection handling, system re-initialization, integration coverage, and a Workbench UI for triggering resets in development builds.
Added
Changed
Fixed