Release 2.0.0-alpha.8 - #172
Merged
Merged
Conversation
Sync develop after 2.0.0-alpha.7 release
…ge-outside-templates TEDEFO-5133: Select preferred language only when translating view templates
TEDEFO-5142, TEDEFO-5144: Transpile EFX selectors to element paths
Publish when a release is published, not when it is created
Check the javadoc on every push
Publish a version once, when its release is published
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 2.0.0-alpha.8
Incremental release over 2.0.0-alpha.7.
Changes
&{reference}in EFX-1, and&{reference}orWITH context SELECT referencein EFX-2. The first use of it isprivacy.undisclosedFieldSelector, which has to name the elements a notice viewer must withhold from publication.context::fieldnow keeps the walk to its context, and any predicate written on that context. Until now the walk was shortened away and a written predicate was discarded, so${field}and${context::field}transpiled to the same thing and the override had no effect at all.Impact on generated output
Expressions using a context override produce a longer path than before, one that yields nothing where the context is absent, and one that applies any predicate written on the context.
No SDK content is affected: context overrides are not used in any released SDK — every occurrence of
::in 1.13.3, 1.14.2, 1.15.1, 1.16.0-beta.2 and 2.0.0-alpha.3 is theprecedingaxis.A predicate written on a node context attaches to a
..step, for example../..[PathNode/IndicatorField = true()]. That is valid XPath 2.0 and is rejected by XPath 1.0.XPathContextualizer.jointakes a third argument and no longer offers the two-argument form. The toolkit is at a major version boundary, and a two-argument overload could only keep old callers working by applying the shortening this release exists to stop.Release metadata
2.0.0-SNAPSHOT→2.0.0-alpha.8.eforms-sdk-1=1.16.0-beta.2,eforms-sdk-2=2.0.0-alpha.3.eforms-coreis at1.9.0-SNAPSHOTand must be pinned to1.9.0before this is merged.Local
mvn clean testpasses (1381 tests, 0 failures).