bug: Ensure q:key is included when a user adds a new key

[JerryWu1234]

Fix ensure q:key is included when a user adds a new key

• Feature / enhancement
• Bug
• Docs / tests / types / typos
• Infra

Description

Checklist

• My code follows the developer guidelines of this project
• I performed a self-review of my own code
• I added a changeset with pnpm change
• I made corresponding changes to the Qwik docs
• I added new tests to cover the fix / functionality

[changeset-bot]

⚠️ No Changeset found

Latest commit: 89c1e78

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/@builder.io/qwik@7049

npm i https://pkg.pr.new/@builder.io/qwik-city@7049

npm i https://pkg.pr.new/eslint-plugin-qwik@7049

npm i https://pkg.pr.new/create-qwik@7049

commit: 89c1e78

[wmertens]

This looks correct, but why is this needed? Is there a bug related to it?

Keys can be really long and this would potentially add a lot of bytes to the HTML output.

[JerryWu1234]

This looks correct, but why is this needed? Is there a bug related to it?

Keys can be really long and this would potentially add a lot of bytes to the HTML output.

#7047

it's weird,

When a list is rendered on the client side, adding more items to the list triggers a re-render. However, only the first

element has a q:key property in the initial render, while the rest lack it.

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
qwik-docs	✅ Ready (View Log)	Visit Preview	89c1e78