Skip to content

feat: implement filter for transaction properties #73

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.

Sign up for GitHub

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

Jump to bottom
Merged
scarmuega merged 2 commits into from
Sep 1, 2022
Merged

feat: implement filter for transaction properties #73

scarmuega merged 2 commits into from
Sep 1, 2022

Conversation

@jmhrpr
Copy link
Contributor

@jmhrpr jmhrpr commented Aug 30, 2022 •
edited
Loading

Initially the only property is is_valid - you can filter to only process transactions which are invalid by using the config:

    "reducers": [
        {
            "type": "TxByHash",
            "key_prefix": "c1",
            "filter": {
                "transaction": {
                    "is_valid": false
                }
            }
        }
    ],

We also add the possibility of using filters with the TxByHash reducer.

In the future the transaction filter can be extended to match transactions which mint a certain asset in the txmint field, or transactions whose metadata contains a specific key.

@jmhrpr jmhrpr requested a review from scarmuega as a code owner August 30, 2022 23:24
@scarmuega scarmuega merged commit fda931b into txpipe:main Sep 1, 2022
@jmhrpr jmhrpr deleted the feat/tx-is-valid-filter branch September 1, 2022 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@scarmuega scarmuega Awaiting requested review from scarmuega scarmuega is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jmhrpr @scarmuega