Checking for empty array on fact

Open
#282 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

The issue names no files, tests, or entry points. Start by tracing how fact values are evaluated and compared, then clarify whether empty-array checks, array-length comparisons, or both are required; done should include agreed behavior and coverage for the selected cases.

Written by the indexing model from the issue text.

Description

Is it possible to check for an array being (not) empty as a fact value? Or, perhaps it would be more flexible to be able to do array length comparisons?

Dominant language
JavaScript
Stars
3.1k
Forks
507
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CacheControl/json-rules-engine

All issues in CacheControl/json-rules-engine

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.