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 Vitest: Fix indentation of 'vitePluginNext' in generated Vitest config file #29011

Merged
merged 1 commit into from
Sep 2, 2024

Conversation

ghengeveld
Copy link
Member

@ghengeveld ghengeveld commented Aug 30, 2024

Fixes this indentation issue:

image

Greptile Summary

This pull request addresses a minor indentation issue in the Storybook Vitest addon's config file generation.

  • Modified code/addons/vitest/src/postinstall.ts to correct the alignment of the vitePluginNext() call in the generated Vitest config
  • Improves readability and maintains consistent code style in the generated configuration
  • Enhances the overall quality of the automatically generated Vitest setup for Storybook projects

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.

LGTM

1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings

Copy link

nx-cloud bot commented Aug 30, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit f4ab3a4. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 1 target

Sent with 💌 from NxCloud.

@yannbf yannbf merged commit f3a34cb into next Sep 2, 2024
55 of 57 checks passed
@yannbf yannbf deleted the fix-vitest-postinstall-indentation branch September 2, 2024 12:48
@github-actions github-actions bot mentioned this pull request Sep 2, 2024
9 tasks
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