generated from TrueCloudLab/basic
Revise MorphRuleChainStorage interface and introduce ContractStorageReader #54
No reviewers
Labels
No labels
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/policy-engine#54
Loading…
Reference in a new issue
No description provided.
Delete branch "aarifullin/policy-engine:feat/contract_storage_reader"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
WIP: Revise MorphRuleChainStorage interface and introduce ContractStorageReaderto Revise MorphRuleChainStorage interface and introduce ContractStorageReader822691ec50
to33585fa7ca
Revise MorphRuleChainStorage interface and introduce ContractStorageReaderto WIP: Revise MorphRuleChainStorage interface and introduce ContractStorageReaderHow about just implementing unwrappers here?
So we will use auto-generated bindings in node, and call
unwrap.ListOfChains
on the result.This reduces the number of wrappers we have.
EDIT: nvm, wrappers are still useful for the types we accept.
Should we use new
MorphRuleChainStorageReader
in router and maybe inEngine
then?It seems they use read only methods
Why is it WIP?
WIP: Revise MorphRuleChainStorage interface and introduce ContractStorageReaderto Revise MorphRuleChainStorage interface and introduce ContractStorageReaderEngine
should be able to change its state by adding/removing rules. So, only router should use...Reader
33585fa7ca
to4154899cff