Ironclad / Ironclad/rivet

[Bug]: Match node matches wrong

Open
#337 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
4.7k
Forks
388
PR merge metrics
No merged PRs in 30d

Description

### What happened?

I have an array of objects that looks like this:

```
{
"fn_name": "{{fn_name}}",
"values": {
"fn_arguments": "{{fn_arguments}}",
"response_message": "{{response_message}}"
}
}
```

fn_name can sometimes be null (which is what I suspect is causing issues)

I destructure it to get fn_name and values (so far so good) to pass to the match node as test and value inputs respectively.

Say fn_name is something like ['fn1', 'fn2', null, null] and the match node has fn1 and fn2 to match against. Match will match all 4 of them against fn1.

### What was the expected functionality?

Expected fn1 to match against fn1, and null to match against unmatched.

### Describe your environment

Windows, Rivet 1.7.7.

### Relevant log output

_No response_

### Relevant screenshots

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.