I'd like to have option to disable the creation of 'test' folder, and put the test file outside per our repo's style. Also if there is an option to decide whether the name is *.test.tsx or *.spec.tsx would be great

This is no longer needed in most cases thanks to the new JSX transform:

https://reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html

When generating a stories file, we are presented with errors on the import statment:

'@storybook/react/types-6-0' import is restricted from being used. Import types from @storybook/react instead

Switching to import as suggested presents this error:

NOTE that in Storybook 7.0, this type will be renamed to StoryFn and replaced by the current StoryObj type.

'Story' import from '@storybook/react' is restricted. Avoid using Story and ComponentStory. Use StoryFn/ComponentStoryFn for function stories (CSF v2), or StoryObj/ComponentStoryObj for object stories (CSF v3). See https://storybook.js.org/blog/component-story-format-3-0/ and https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#storyobj-type

When people land on this repo, it'd be great if they had a way to quickly install the Extension.

I suggest setting https://marketplace.visualstudio.com/items?itemName=AndrewMcGoveran.react-component-generator as the URL for this repo.

I like to organize my components by type.
For example:
-components
-dialogs
-dialogcomponent1
-dialogcomponent2
-lists
-todoList
-shoppingList
etc..

If right clicking the dialogs folder and selecting to Generate a new react component it will add a components folder under the dialogs.
I would like to have a setting to avoid this.

When generating a JS component, an invalid interface is included:

https://github.com/andrewmcgov/react-component-generator/blob/main/src/templates/reactFunctionComponentTemplate.ts#L13-L15

Pointed out in #27

Suggested in #27

• Allow for importing CSS without a module reference
• Allow for a default classname on the generated component

When right clicking a directory and selecting "Generate Storybook stories file", it'd be nice if the component name was pre-populated in the prompt field, or even better if there weren't even any prompts and the file was directly created.

Hi! I wonder if there is any plan to update the storybook template to adopt CSF3?

• Use named exports everywhere
• Import the styles and add className={styles.ComponentName} to the rendered div
• Pre-populate the Sass file with a .ComponentName rule
• Declare an interface named ComponentNameProps
• Use export * …. in the ComponentName/index.ts file
• Add setting to generate story when making component
• Add command to add story to an existing component
• Remove styles and tests settings
• Add verbose story comments setting
• Don’t update app/components/index.ts
• Update readme
• Update changelog