-
Notifications
You must be signed in to change notification settings - Fork 26
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
clarify property() function #57
Comments
@lognaturel writes:
Yes, that would be good. And not document it at all perhaps. |
I think removing it from the spec for now is fine. It's ok to have things in JavaRosa that aren't part of the spec. Ideally in the near future JR will get its own documentation that amends this spec with any relevant implementation details and extra features. When you suggest replacing "preload items with an external session instance like CommCare ", you mean having an external XML document that holds session information and which is retrieved as an external instance as per #50, is that correct? |
What are the exact property() parameter values that JavaRosa supports? |
Oops, totally missed this. Here is the relevant code, I believe. It accepts a single string parameter which represents the name of the desired property managed by the And to confirm, you are talking about #50 as a possible way to hold session information, right? |
Thanks. I see these:
Yes, I think I agree. I did coincidentally see a query from Esri about this function and I've asked them for their use case for it (that is not equally well met by preload items). Maybe there is one.
Yes |
To be removed as part of #189 fix. |
To be done in a way that we can present this as an XPath function (regardless of how exactly it's implemented in JavaRosa or Enketo (it is not)). This is not easy imo.
It would be easy if/once we replace preload items with an external session instance like CommCare because in that case
property(PROP)
is just a shortcut for obtaininginstance('session')/PROP
or something similar.The text was updated successfully, but these errors were encountered: