PLEX-2773: Support both include reverted states#1563
Conversation
6b59576 to
c922e7a
Compare
f5f6fa0 to
2d99eac
Compare
2d99eac to
d6689e0
Compare
📊 API Diff Results
|
|
📊 API Diff Results
|
f9f12f7 to
8154840
Compare
8154840 to
cb18231
Compare
|
| } | ||
|
|
||
| // ensure that the value of IncludeReverted isn't different from any other filters with the same address and event type | ||
| if contractFilters, okAddr := fl.filtersByAddress[filter.Address]; okAddr { |
There was a problem hiding this comment.
Until CCIP starts passing the filter name we should keep this logic, but hide it behind feature flag that is enabled by default and disabled for CRE
| // FilteredLogs runs a DSL query against stored logs. When queryName is set, results are | ||
| // scoped to that registered filter (filter_id in SQL, no dedup). An empty queryName is the | ||
| // legacy path: query all filters for the chain and dedupe by (block_number, log_index). | ||
| func (o *DSORM) FilteredLogs(ctx context.Context, filter []query.Expression, limitAndSort query.LimitAndSort, queryName string) ([]types.Log, error) { |
There was a problem hiding this comment.
This is a breaking change that occurs at runtime, leading to hard-to-track bugs.
You are re-proposing a previously existing function argument. Previously it was queryName, and now it's filterName.
If someone imported DSORM and passed a non-empty queryName, now it'll be treated as filterName
| logsFields = [...]string{"chain_id", "log_index", "block_hash", "block_number", "block_timestamp", "address", | ||
| "event_sig", "tx_hash", "data", "error"} | ||
|
|
||
| scopedLogsFields = [...]string{"filter_id", "chain_id", "log_index", "block_hash", "block_number", "block_timestamp", "address", |
There was a problem hiding this comment.
Do we use filter_id from the Logs structure after select? I'm worried that the field's presence depends on the filter value.



Description
Requires Dependencies
Resolves Dependencies