graphprotocol / graphprotocol/graph-node
Feature request: Filter based on failure of some criteria and using multiple filters in the same query
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 1.1k
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 1
Description
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
It is not possible to use a global _not while filtering to negate a condition, just like described here:
https://hasura.io/docs/1.0/graphql/manual/queries/query-filters.html#filter-based-on-failure-of-some-criteria-not
It would be interesting to have this feature in combination with 'and' or 'or' operators (which are not implemented as well) to create arbitrarily complex boolean expressions involving multiple filtering criteria.
I believe this could help some specific filtering use-cases.
Thank you
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue mentions GraphQL query filters and links to Hasura's filtering documentation, but names no repository files, tests, or entry points. Start by locating graph-node's GraphQL filter parsing and query-building entry points, then define tests covering negation and combined and/or criteria, including nested boolean expressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100