open-feature / open-feature/flagd
[CHORE] Investigate and document JSON Logic consistency issues
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 998
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
JSONLogic is used as the basis for all our flagd implementations (the evaluator inside the flagd bin/daemon itself, and inside the in-process providers). However, JSONLogic implementations have some noted inconsistencies. Not all of them may impact us, and some of them might have workarounds (ie: we can avoid support for some shorthands with our schema).
We need to enumerate and understand these, and then:
- File relevant issues
- Brainstorm solutions (e.g. WASM module, etc)
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
Start with the JSON Logic compatibility tables, then compare their findings against the evaluator in the flagd bin/daemon and the in-process providers. Document which inconsistencies affect flagd, note possible schema workarounds, file relevant issues, and record solution ideas such as a WASM module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100