Open Issues Need Help
View All on GitHub[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: The `@asyncapi/parser` is critically slow, missing performance targets by 5-10x, making it unsuitable for production. For instance, a simple document takes 5.2 seconds instead of the desired <500ms. The primary issues identified include creating a new parser instance per validation call, multiple validation passes, a lack of caching, and an ineffective fast-path, all contributing to the severe performance degradation.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: This GitHub issue reports a major success in migrating to Effect.TS Railway Programming, achieving 90% completion and production-ready implementation. It details the resolution of critical anti-patterns, including fixing `Effect.runSync` in constructors, improving path validation error handling, and standardizing service architecture with pure Effect.TS patterns. The update highlights significant progress in enhancing functional composition and testability.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: The project is experiencing a critical "architectural crisis" due to a "split brain" scenario where three different `ValidationResult` types exist across the codebase. This inconsistency is causing TypeScript compilation failures, blocking all development, and leading to runtime type safety issues. The immediate task is to unify these disparate types into a single, canonical `ValidationResult` definition to restore type safety and development flow.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: The MQTT plugin has been implemented but is not yet registered within the main plugin system, preventing its use with TypeSpec and generation in AsyncAPI documents. The task involves registering the `mqttPlugin` in `plugin-system.js`, adding it to `registerBuiltInPlugins()`, and then verifying its functionality through TypeSpec examples and AsyncAPI output. This is a high-priority task to ensure complete protocol coverage.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: A critical bug is causing TypeSpec's property enumeration APIs, specifically `walkPropertiesInherited()`, to return empty iterators for models. This occurs despite models having defined properties in the TypeSpec source, leading to empty schema conversions and blocking hundreds of tests.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: This issue proposes a "quick win" to fix test output paths across approximately 50 test files. Applying this fix is expected to enable 150-170 additional tests to pass, significantly increasing the overall test pass rate from 75% to over 96%. The estimated effort is 1-2 hours, leveraging a proven pattern from a previous commit.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: This issue aims to eliminate the final 27 ESLint violations to achieve 100% code quality compliance. It involves addressing 14 `no-this-alias` violations by applying functional patterns, fixing 6 `Promise` anti-patterns by migrating to `Effect.TS` constructs, removing 2 accidental `try/catch` blocks, and resolving 5 minor issues.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: This issue aims to extract existing protocol-specific bindings (Kafka, WebSocket, HTTP, and future MQTT/AMQP) from the core emitter into separate, standalone plugins. This initiative is crucial for enhancing maintainability, enabling community extensibility, and fully leveraging the recently established modular architecture. The task involves creating new plugin structures, migrating code, implementing a robust plugin discovery and loading system, and enabling hot-reload capabilities.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: This issue proposes removing Vitest from the project, as it's installed but unused, leading to dependency bloat and confusion. The project already exclusively uses Bun's native test runner, which offers superior performance, zero-config setup, and built-in features like coverage. The solution involves uninstalling Vitest and deleting its configuration files.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: This issue proposes a comprehensive refactor to eliminate all traditional `try-catch` blocks from the codebase, replacing them with `Effect.TS`'s dedicated error handling patterns like `Effect.try` and `Effect.catchAll`. The goal is to enhance type safety, ensure 100% error visibility, and leverage Effect.TS's superior error tracking, composability, and debugging capabilities. This change aims to align the codebase fully with the Effect.TS 'railway programming' paradigm for error management.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: The `createAsyncAPIBinding()` helper function correctly generates protocol binding objects, but these bindings are not being serialized or included in the final AsyncAPI YAML output. This results in missing `bindings:` sections in channels, operations, and messages, despite the core generation and plugin system working as expected.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: This issue proposes a critical migration to replace the project's extensive custom AsyncAPI protocol bindings (over 5000 lines of code) with official, standardized AsyncAPI bindings. The current custom implementation leads to ecosystem fragmentation, high maintenance burden, and breaks interoperability with AsyncAPI tooling, while the migration aims to leverage existing solutions and improve compatibility.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: The current TypeSpec test mock infrastructure is causing significant instability and 117 test failures due to basic program mocks, inconsistent test environments, and a mismatch between test program structure and production emitter expectations. This enhancement aims to create sophisticated program mocking capabilities, including full TypeSpec compiler integration, to improve test reliability, accelerate development, and ensure production confidence.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: A critical architectural issue has been identified where a 'Ghost Error System' (legacy, scattered, inconsistent) exists alongside the production-ready, centralized error handling system. The goal is to audit all error handling, consolidate or migrate the ghost patterns to the main system, remove duplicates, and update documentation to ensure a single source of truth for error handling.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: This issue proposes the immediate deletion of over 2600 lines of identified "ghost code" across four specific files/directories: `integration-example.ts`, `lib-enhanced.ts`, `performance/`, and `protocol-bindings.ts`. These files are deemed unused, unintegrated, over-engineered, and are causing confusion, maintenance burden, and false complexity within the codebase. An action plan is provided to remove them, aiming for a cleaner and clearer architecture.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: The project's TypeScript compilation is failing, preventing the generation of `dist/index.js` and blocking critical end-to-end testing for server and message integration. The issues stem from missing `downlevelIteration` flag required by `Effect.TS` and module resolution problems with `@typespec/asset-emitter`, indicating `tsconfig.json` misconfiguration and complex type interactions.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications
AI Summary: The codebase contains 432 instances of `console.log` across 35 files, leading to unstructured and unfilterable logging output. The proposed solution is to replace these with a structured logging system using Effect.TS Console service, enabling proper log levels, contextual output, and filtering for a production-ready solution.
[WARNING-VERY_EARLY_DEVELOPMENT] TypeSpec emitter for AsyncAPI 3.0 specifications