-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
XPathDOMAdapter &co refactor: prologue
As of the previous commit, I still have a few uncommitted changes in the `@getodk/xpath` package. This commit incorporates all but one remaining change. Most of this is just commentary. **SUBSTANTIVE CHANGE: eliminate unnecessary `tee` call** The last change to LocationPathEvaluation is a little bit of a perf optimization freebie. The call here to `tee` has not been necessary for some time, if it ever was. It’s highly likely it was introduced in early prototyping, while debugging some unexpected iterable/iterator behavior. The call is pure overhead, which I’ve known for some time but haven’t had a good excuse to land this quick win. However, this is probably the ideal time to take the quick win: it will give us a less biased baseline for comparing downstream (i.e. `@getodk/xforms-engine`) performance: 1. Before: evaluating XForms expressions against the current WHAT DOM backing store 2. After: evaluating those same expressions against the engine’s own DOM representation (which will be expanded to incorporate the functionality commited up to this point, and broadly to begin supporting external secondary instances). **WHAT’S NEXT: one last `@getodk/xpath` change** The next commit will set the stage for integration of the preceding changes into `@getodk/xforms-engine`, by restoring the export of `XFormsXPathEvaluator` (currently a temporary alias to the WHAT DOM equipped `DefaultXFormsXPathEvaluator`) so its breaking changes can be integrated. Once downstream integration is complete, we can finally dispatch `DefaultXFormsXPathEvaluator` to its test-only fate!
- Loading branch information
1 parent
de08826
commit 92f41b7
Showing
5 changed files
with
38 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters