Skip to content
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

Addon-themes: Make type generic less strict #26042

Merged
merged 1 commit into from
Feb 15, 2024
Merged

Conversation

yannbf
Copy link
Member

@yannbf yannbf commented Feb 15, 2024

Closes #25042

What I did

Changed the generics from Addon-themes decorators so they're less strict. @kasperpeulen mentioned that at some point in the future he could write a guide to create proper inferrable decorators, but for now we just make the types less strict, which will solve issues where people do not specify those generics such as:

withThemeByClassName()

instead of

withThemeByClassName<ReactRenderer>()

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/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>

@yannbf yannbf added the patch:yes Bugfix & documentation PR that need to be picked to main branch label Feb 15, 2024
@kasperpeulen
Copy link
Contributor

Merge it!!

@yannbf yannbf merged commit 999fc2a into next Feb 15, 2024
60 of 63 checks passed
@yannbf yannbf deleted the yann/fix-addon-themes-types branch February 15, 2024 10:58
storybook-bot pushed a commit that referenced this pull request Feb 15, 2024
Addon Themes: Make type generic less strict

(cherry picked from commit 999fc2a)
@github-actions github-actions bot added the patch:done Patch/release PRs already cherry-picked to main/release branch label Feb 15, 2024
@shilman shilman changed the title Addon Themes: Make type generic less strict Addon-themes: Make type generic less strict Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addon: themes bug ci:normal patch:done Patch/release PRs already cherry-picked to main/release branch patch:yes Bugfix & documentation PR that need to be picked to main branch typescript
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: setProjectAnnotations typescript error when decorators has withThemeFromJSXProvider
3 participants