Matching nodes bug

Open
#10 0 comments 0 reactions 1 assignee View on GitHub

@mitchellsundt is already working on this.

Since Feb 1, 2017.

Assessment

This issue has not been assessed yet.

Description

bug

Issue by mitchellsundt
Thursday Jul 09, 2015 at 19:03 GMT
Originally opened as https://github.com/opendatakit/opendatakit/issues/692 (0 comment(s))


Originally reported on Google Code with ID 691

If you have instance like so..

<instance>
        <data id="no_matching_modes">
          <Interviewer/>
          <District/>
          <Cluster/>
        </data>
</instance>

And some binds like so...

      <bind nodeset="/cluster/Date" required="true()" type="date"/>
      <bind nodeset="/cluster/Interviewer" required="true()" type="string"/>
      <bind nodeset="/cluster/District" required="true()" type="string"/>

Currently, Validate (or Collect) do not throw up any errors. It is only at runtime
that you know something is wrong -- Collect crashes.

See the problem? There is no /cluster in the instance, only /data. The binds are referring
to nodes that don't exist. I believe earlier versions of Validate caught this matching
nodes problem.

Reported by [email protected] on 2012-09-26 17:07:31


- _Attachment: [Matching nodes bug.xml](https://storage.googleapis.com/google-code-attachments/opendatakit/issue-691/comment-0/Matching nodes bug.xml)_
Dominant language
Java
Stars
14
Forks
32
Avg merge
14h 15m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getodk/validate

All issues in getodk/validate

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.