fix: decouple runtime from graph config #190
Open
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.
Description
This PR decouples the runtime from graph configuration by introducing a new
LangGraphScriptRuntime
class and aGraphResolver
to handle graph loading. The changes separate concerns by removing graph configuration logic from the runtime and moving it to a dedicated resolver pattern.LangGraphScriptRuntime
as a specialized runtime for script-based executionGraphResolver
to handle graph loading and configuration validationThis change also introduces
GraphResolverContext
, an async context manager that wraps the existingGraphResolver
and returns a callable compatible withLangGraphRuntime
. It ensures that the underlying graph is loaded only once, improving performance and efficiency when executing multiple runtimes with the same entrypoint.Development Package