Martijn van de Rijdt

> I believe openrosa-xpath-evaluator will need to be able to provide some kind of metadata about the nodes matched in arbitrary XPath expressions, and enketo-core will need to use that...

Thanks a lot for sharing! Will leave this out here for now. @magicznyleszek is working on a fancy documentation system for all Enketo repos (see PR in this repo) and...

@shankari, Certainly! You can use the one referenced in the source of the [README.md](https://raw.githubusercontent.com/enketo/enketo-core/master/README.md) at the bottom. > We definitely want to give credit to your cool library, but would...

Thanks! Forgot to mention, that I'd be happy to promote your app on the Enketo.org front page (free). Just send a logo and link or open an issue with those...

Thanks. Looks like a serious bug!

http://localhost:8005/?xform=00_test_bugs.xml * [x] check removing calculation - issue does not occur so likely not caused by relevant * [x] check removing relevant - haha, also does not occur, so it's...

or two modes (that with flexible names so we can add/remove things): * ~~`legacy` (whether old incorrect forms should be supported), default true~~ * `speedup/turbo` (performance boosts with reduced syntax...

Instead of a `legacy` mode it would be even cooler if pyxform added an attribute or class to indicate major changes such as `no-repeat-reference-bug`. Clients could then disable the workaround...

It's probably this ODK Validate workaround: https://github.com/XLSForm/pyxform/issues/87#issuecomment-249008655 (some dummy content that pyxform adds). Check the XForm to confirm. I think this workaround can actually be removed from pyxform now (if...

Thanks for following up! So it sounds like this may still be a bug in Enketo though. Will check.