hasura / hasura/graphql-data-specification
Clarify Predicate functions expressiveness and flexibility
- Dominant language
- No language data
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I'm trying to understand the spec in its current form. Could you clarify how expressive predicate functions you intend predicate functions to be? Specifically, can they be defined as arbitrary functions using some simple scripting language? Or is it limited to a few keywords? In either case, can you elaborate on the goals and constrains that informed your current thinking?
Best,
J
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the current specification's treatment of predicate functions and the question about arbitrary scripting versus a limited keyword set. Clarify the intended expressiveness, goals, and constraints in the specification once the maintainers have decided the direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100