fix(webpack): xml-namespace-loader incorrect dependency mapping #9780
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.
PR Checklist
What is the current behavior?
In some cases
xml-namespace-loaderwould add/register a global module without a suffix pointing to the xml file - which is incorrect because no-extension modules are reserved for code modules (ts/js). This resulted in the wrong context being passed to the custom component and failing to bind properly.What is the new behavior?
We should now detect the "fallback" case - and not register the extensionless modules pointing to the
xmlfiles.This partially fixes #9730 - when using a
<Button>the taps are correctly handled by the parent context handler. For some reason, unrelated to this as far as I can tell, the tap event is not emitted from the<Label>inside the ActionBar.fixes #9730