-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(engine): marking dynamic nodes as dynamic #810
Conversation
Benchmark resultsBase commit: lwc-engine-benchmark
|
Benchmark resultsBase commit: lwc-engine-benchmark
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with this! It is a perf-regression in some degree, but probably very small because no everybody is using the template for the if
condition.
<template> | ||
<template if:true={hasParts}> | ||
<template for:each={text} for:item="part"> | ||
<template if:true={part.highlight}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we simplify this by removing part.highlight
from the picture?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oddly enough, the bug does not exhibit when we remove this condition,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -458,15 +458,15 @@ export function f(items: any[]): any[] { | |||
} | |||
const len = items.length; | |||
const flattened: VNodes = []; | |||
|
|||
// all flattened nodes should be marked as dynamic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is that?
|
||
it('should not render duplicate text', function () { | ||
browser.click('integration-duplicate-text-rendering'); | ||
assert.deepEqual(browser.getText('integration-duplicate-text-rendering'), 'b'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it worth adding an assert.notDeepEqual()
here, or maybe a comment that describes the issue that these changes fix? I'm just curious about what was actually being rendered.
Benchmark resultsBase commit: lwc-engine-benchmark
|
Benchmark resultsBase commit: lwc-engine-benchmark
|
Details
Fixes a text rendering issue in
baseCombobobxFormattedText
. Switching between an iterator and a plain text node was causing duplicate text to render.Does this PR introduce a breaking change?