Skip to content

feat: Filter values in the Manifest output #565

@piotr-roslaniec

Description

@piotr-roslaniec

Comment on the current status of the work:

  • With changes from feat: Support advanced response matching in Manifest #518, the predicates are used to test the validity of the values extracted from the notary response. However, predicates are not used for filtering. As a result, we are returning not just the values described by the predicates but other values.
  • For example: Let's say a predicate describes an array that contains a "TEST" string. All the following values (arrays) are therefore considered as valid and will be returned entirely: ["TEST"], ["TEST", "OTHER"], ["TEST", "OTHER_1", ... "OTHER_N"]
  • Should we use predicates to enable value filtering? If we do, all of the three values above would be reduced to ["TEST"]

Originally posted by @piotr-roslaniec in #514

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions