CacheControl / CacheControl/json-rules-engine
Question: Comparing Distinct Arrays of Objects
- Langage dominant
- JavaScript
- Étoiles
- 3.1k
- Forks
- 507
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Hello,
I am trying to compare an array of objects to check for a specific set of objects to be present in any of them, but not across all of them, specifically lets take this rule:
```
const arrayRule = {
conditions: {
any: [
{
all: [
{
fact: 'data',
path: '$.[*].equalityTest',
operator: 'equal',
value: 50,
},
{
fact: 'data',
path: '$.[*].anotherTest',
operator: 'equal',
value: 50,
},
],
},
],
},
event: {
type: 'arrayRule',
},
};
```
This is the first iteration of the rule I came up with, it is incorrect, but I wanted to give an idea of what I am aiming for.
Specifically here, we have a rule where I want `equalityTest` to equal `50` and `anotherTest` to also equal `50`. But I want them to equal those values in the same object, such that:
*THIS SHOULD RETURN FALSE*
```
const facts = {
data: [
{
anotherIntegerFact: 1,
equalityTest: 50,
},
{
anotherIntegerFact: 50,
equalityTest: 40,
},
],
};
```
*THIS SHOULD RETURN TRUE*
```
const facts = {
data: [
{
anotherIntegerFact: 50,
equalityTest: 50,
},
{
anotherIntegerFact: 40,
equalityTest: 40,
},
],
};
```
Would love any suggestions or ideas on a way to tackle this. One thought was I could write my own `operator` and add it to the registry of operators on our end, but before I did so, I wanted to validate that is needed.
Thanks
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Aucun point d’entrée de fichier ou de test n’est indiqué. Commencez par examiner la condition de règle et le registre des opérateurs autour de l’évaluation des chemins de tableaux ; utilisez les deux exemples de facts fournis pour définir l’achèvement comme une correspondance du même objet renvoyant false pour le premier et true pour le second.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript
- Domaine
- backend
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 20/100