Skip to content

Throw error in case multiple fields / field options are matched #32

@gr2m

Description

@gr2m

Please avoid duplicates

Reproducible test case

No response

Please select the environment(s) that are relevant to your bug report

  • Browsers
  • Node
  • Deno

Versions

1.3.1

What happened?

In theory, a field configured in the fields constructor option can be matched to multiple project fields when using the matchFieldName constructor option. The same is true for matching field options and the matchFieldOptionValue option.

I think right now the first match wins. But what we should do instead in both cases is to match all fields / field options respectively and verify that there is exactly one match. We throw an error if there is no match. We should also throw an error if there is more than one match

Would you be interested in contributing a fix?

  • yes

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions