Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete subexpression detection #35

Open
lognaturel opened this issue Feb 18, 2024 · 1 comment
Open

Complete subexpression detection #35

lognaturel opened this issue Feb 18, 2024 · 1 comment

Comments

@lognaturel
Copy link
Member

No description provided.

@eyelidlessness
Copy link
Member

eyelidlessness commented Feb 20, 2024

Just a couple quick notes for clarity of what I think this issue covers:

  • The intent of subexpression detection (and related functionality) thus far is to establish dependency relationships between a given form instance node and other aspects of the form
  • This includes, but is not limited to, location path references resolving to other instance nodes
  • Already-implemented examples going beyond references to other instance nodes include:
    • Translations (calls to jr:itext()) establish a dependency on the active language
    • Itemsets (when calls to instance()) establish a dependency on the referenced secondary instance (and the data referenced therein); these may also include predicates (choice filters in XLSForms lingo) which establish dependencies to primary instance nodes

This last point is potentially a beneficiary of #17 (or other potential solutions to the same motivating problem): if an instance() expression includes a predicate with an absolute reference to a repeat descendant (as many of the existing fixtures I'm familiar with do), we'll need to be able to contextualize those dependencies appropriately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants