-
Notifications
You must be signed in to change notification settings - Fork 5
RPC Rework: Part 2: Rename ModuleBlueprintSet to Blueprint
#1139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
…lueprint to be consistent with docs
Greptile OverviewGreptile SummaryThis PR performs a clean rename refactoring: Key changes:
Files requiring attention:
Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant User
participant Module
participant Blueprint
participant _BlueprintAtom
participant autoconnect
Note over User,autoconnect: Before: ModuleBlueprintSet, ModuleBlueprint, create_module_blueprint
Note over User,autoconnect: After: Blueprint, _BlueprintAtom, Blueprint.create
User->>Module: Module.blueprint()
Module->>Blueprint: Blueprint.create(Module, *args, **kwargs)
Blueprint->>_BlueprintAtom: _BlueprintAtom.create(Module, args, kwargs)
_BlueprintAtom->>_BlueprintAtom: Extract connections from In/Out annotations
_BlueprintAtom-->>Blueprint: Return _BlueprintAtom instance
Blueprint-->>Module: Return Blueprint(blueprints=(_BlueprintAtom,))
Module-->>User: Return Blueprint instance
User->>autoconnect: autoconnect(blueprint1, blueprint2, ...)
autoconnect->>autoconnect: Merge all _BlueprintAtom instances
autoconnect->>autoconnect: Combine transport_map, config_overrides, etc.
autoconnect-->>User: Return combined Blueprint
User->>Blueprint: .transports({...}) / .global_config(...) / .remappings(...)
Blueprint-->>User: Return new Blueprint with updated configuration
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 file reviewed, 1 comment
Additional Comments (1)
|
No description provided.