Skip to content

Conversation

@DamianGlowala
Copy link
Contributor

@DamianGlowala DamianGlowala commented Jul 12, 2025

What I did

This avoids having to cast types as in https://github.com/nuxt-modules/storybook/pull/924/files#diff-4657809e34640547f8b12e905d8465bb32ac3e1187e7ee47f7758d8dcb661dacR28-R29

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

  • stories
  • unit tests
  • integration tests
  • end-to-end tests

Manual testing

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

Documentation

  • Add or update documentation reflecting your changes
  • If you are deprecating/removing a feature, make sure to update
    MIGRATION.MD

Checklist for Maintainers

  • When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli-storybook/src/sandbox-templates.ts

  • Make sure this PR contains one of the labels below:

    Available labels
    • bug: Internal changes that fixes incorrect behavior.
    • maintenance: User-facing maintenance tasks.
    • dependencies: Upgrading (sometimes downgrading) dependencies.
    • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
    • cleanup: Minor cleanup style change. Will not show up in release changelog.
    • documentation: Documentation only changes. Will not show up in release changelog.
    • feature request: Introducing a new feature.
    • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
    • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

Greptile Summary

Added generic type parameter support for host element types in Vue 3 renderer's setup function, improving type safety for framework integrations like Nuxt.js.

  • Added AppHostElement generic type parameter to Vue 3 renderer setup function in code/renderers/vue3/src/render.ts
  • Eliminates need for manual type casting when specifying custom host element types
  • Maintains existing functionality while enhancing type safety
  • Compatible with Vue 3's typing system and Storybook's component model

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 file reviewed, 1 comment
Edit PR Review Bot Settings | Greptile

@github-actions github-actions bot added the Stale label Aug 4, 2025
@github-actions github-actions bot added the Stale label Oct 17, 2025
@valentinpalkovic valentinpalkovic changed the title Update Vue 3 renderer's setup function to allow passing generic HostElement type Vue3: Update renderer's setup function to allow passing generic HostElement type Dec 9, 2025
@valentinpalkovic valentinpalkovic merged commit feb1a18 into storybookjs:next Dec 9, 2025
47 of 48 checks passed
@github-actions github-actions bot mentioned this pull request Dec 9, 2025
13 tasks
@DamianGlowala DamianGlowala deleted the types/vue3-renderer-setup-fn-generics branch December 9, 2025 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants