This repository was archived by the owner on Dec 15, 2025. It is now read-only.
Decouple EagerNode and Search via EagerEngine interface #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes hard dependency between
ClusterNodeandSearchby introducing anEagerEngineinterface, enabling alternative engine implementations.Changes
Added
EagerEngineinterface defining the engine contract:input(data: string): string | null- returns formatted data or null on rejectionoutput(callback: (result: string) => void): number- executes search roundmeta(): {input: string[], output: string[]}- exposes I/O patternsRenamed
ClusterNode→EagerNodewith constructor signature change:Updated
Searchto implementEagerEngine(methods already matched interface)Replaced non-null assertions with null checks in all
engine.input()call sites:Updated instantiation sites to inject
Searchinstance:Usage
Engines can now be swapped at runtime:
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.