Open Issues Need Help
View All on GitHubAI Summary: The task is to implement a mechanism in the Overwatch state management library that allows users to define a custom type registry (keyRegistry.ts) in their project root. This registry will be used by Overwatch for type safety in its useSharedState and usePicker hooks. The solution must be robust, handling cases where the registry is absent (allowing zero-config usage), and avoiding breaking changes or runtime overhead. Several approaches, such as paths mapping in tsconfig.json, need to be evaluated for their feasibility and developer experience.
It's a super lightweight yet expressive state management library for React Js & Next Js, built on the singleton design pattern. It offers support for global and instance-specific middlewares, immutability, batched updates, and custom event communication — all designed to be used without extensive boilerplate.
AI Summary: Create a small, self-contained starter application demonstrating the Overwatch TS state management library's core features (shared state, usePicker, middleware) and optionally SSR hydration. The starter app should be excluded from the published package and only used for local development and testing. Documentation and an npm script for running the example are also required.
It's a super lightweight yet expressive state management library for React Js & Next Js, built on the singleton design pattern. It offers support for global and instance-specific middlewares, immutability, batched updates, and custom event communication — all designed to be used without extensive boilerplate.
AI Summary: Create a CONTRIBUTING.md file for the Overwatch-TS project, outlining setup instructions, coding standards, testing procedures, issue reporting guidelines, and communication channels for potential contributors.
It's a super lightweight yet expressive state management library for React Js & Next Js, built on the singleton design pattern. It offers support for global and instance-specific middlewares, immutability, batched updates, and custom event communication — all designed to be used without extensive boilerplate.
AI Summary: Improve the documentation and README for the Overwatch state management library to provide clear and concise examples of using Overwatch with React in Server-Side Rendering (SSR) scenarios. The current examples are insufficient and need enhancement for better understanding and usability.
It's a super lightweight yet expressive state management library for React Js & Next Js, built on the singleton design pattern. It offers support for global and instance-specific middlewares, immutability, batched updates, and custom event communication — all designed to be used without extensive boilerplate.
AI Summary: Implement a configuration option in a TypeScript-based React state management library to control the execution order of global and local middlewares. This involves modifying the middleware pipeline to conditionally execute global middlewares before or after local middlewares based on a boolean flag, updating tests, and documenting the change.
It's a super lightweight yet expressive state management library for React Js & Next Js, built on the singleton design pattern. It offers support for global and instance-specific middlewares, immutability, batched updates, and custom event communication — all designed to be used without extensive boilerplate.
AI Summary: Implement a developer tool integration for the Overwatch state management library. This would likely involve creating a browser extension or a standalone application that allows developers to inspect and debug the application's state managed by Overwatch, potentially including features like visualizing the state tree, monitoring state changes, and interacting with the state directly.
It's a super lightweight yet expressive state management library for React Js & Next Js, built on the singleton design pattern. It offers support for global and instance-specific middlewares, immutability, batched updates, and custom event communication — all designed to be used without extensive boilerplate.