v1.2.0
Improvements
- #1687 - template-compiler: Add support for content attributes with leading hyphens. Until now, component authors were able to define component properties in Pascal case but users were not able to set those properties in their templates. Users can now set the value of a Pascal case property by adding a leading hyphen to the attribute (e.g.,
@api FooBar
can be set via-foo-bar={awesomeValue}
) - #1679 - wire-service: Add support for the lowercase event type
wirecontextevent
in addition to the currently supported event typeWireContextEvent
. This allows component authors to avoid engine warnings triggered when using event types with capital letters.WireContextEvent
is now deprecated and will be removed in a future release.
Bug Fixes
- #1676 - synthetic-shadow: Fix a bug in the
Event
polyfill so that the composed option is respected when instantiating an instance ofEvent
. The previous behavior ignored the composed option and only considered the type of the event when accessing the composed property of anEvent
instance. This polyfill exists to normalize the behavior of some browsers that incorrectly set the composed property of natively composed events.
Internal
- #1682: Remove usage of white/black as good/bad. Implements the “tone” guidelines for the WHATWG style guide.
- #1648 - engine: Remove the
instanceof Event
check inLightningElement.prototype.dispatchEvent
. The same check is run by the browser when invoking theEventTarget.prototype.dispatchEvent
method. Reduces the coupling between the engine and the DOM in preparation for server side rendering. - #1668, #1674, #1675: Review all disabled karma integration tests. Enable tests that can be enabled. Remove tests that are no longer relevant. Refactor tests appropriately based on their relevancy (native vs synthetic shadow).
- #1669 - karma-integration: Port existing webdriver integration tests to karma. Delete unnecessary tests. The goal here is to reduce the number of integration tests to the strict minimum to increase the integration test passing rate.
- #1692 - engine: Refactor the way error boundaries are computed by decoupling the logic from the DOM.
- #1683 - features: Fix a bug where unary negation of a runtime feature flag was being interpreted as a compile-time boolean false.
- engine: Improve our usage of internal types.
- #1694 - features: Remove support for feature flags as computed properties. This means that
featureFlags['ENABLE_FOO']
will no longer work and should be referenced asfeatureFlags.ENABLE_FOO
instead. - #1652 - synthetic-shadow: Add
tsc
as part of the build.tsc
should run before rollup to catch TypeScript-related errors.