Add `In` operator edge cases
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- testing
Research direction
Start by reading the linked pull request discussion, then inspect the existing test data for the In operator in this repository. Add the twelve listed native-list, comma-delimited, and JSON-encoded numeric cases, preserving the expected match or non-match outcomes for integer and float types.
Written by the indexing model from the issue text.
Description
See https://github.com/Flagsmith/flagsmith-php-client/pull/115#discussion_r2466356145.
Add the following cases.
Native list condition properties:
- float context value vs float[] condition property — should match.
- int context value vs int[] condition property — should match.
- float context value vs int[] condition property — should not match.
- int context value vs float[] condition property — should not match.
Comma-delimited string condition properties:
- float context value vs string comma-delimited floats condition property — should match.
- int context value vs string comma-delimited ints condition property — should match.
- float context value vs string comma-delimited ints condition property — should not match.
- int context value vs string comma-delimited floats condition property — should not match.
JSON-encoded list condition properties:
- float context value vs string JSON-encoded floats condition property — should match.
- int context value vs string JSON-encoded ints condition property — should match.
- float context value vs string JSON-encoded ints condition property — should not match.
- int context value vs string JSON-encoded floats condition property — should not match.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from Flagsmith/engine-test-data
-
Flagsmith/engine-test-data#49 · 3 comments · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
tech-debt
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Flagsmith/engine-test-data
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fulcrumgenomics/ferro-hgvs#2251 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
personalrobotics/tsr#127 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Flaky: conversation-lifecycle terminal-error gate compares rendered clock time across settle/reload Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nesquena/hermes-webui#7792 ·
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100