Skip to content

Clarification needed: Documentation vs. code behavior for XPaths matching multiple elements #1

@clnsmth

Description

@clnsmth

I'm seeking clarification regarding the behavior of the /raw/ endpoint when an XPath matches more than one element.

Observed behavior:

  • When a supplied XPath matches multiple elements in the EML document, the application returns an error message (as an HTML response) stating that more than one element was found.

Documentation expectation:

  • The current documentation suggests that any XPath can be used with the /raw/ endpoint to retrieve the matching XML fragment. There is no explicit mention that the XPath must match exactly one element, nor that an error will be returned in the case of multiple matches.

Request:

  • Could you clarify whether the documentation or the code reflects the intended behavior?
  • Should the application support returning multiple elements for such XPaths, or should the documentation be updated to describe the current constraint?

Thanks for your help!

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