yeet-bix / create-react-component-vscode Goto Github PK

Current behaviour

After generating a component, nothing happens.

Suggestion

Add option to open the generated files.

Something like:

{
  "createReactComponent.openFiles": ["component", "test", "index"],
}

It would be awesome if we had the option to create context modules that export providers and hooks. I think most of the time, these files are boilerplates.

Input: ContextName
Produces:

• a folder called <ContextName>Context
• index file
• <ContextName>Context.tsx

export * from './__ContextName__Context';

// <ContextName>Context.tsx
import React, { createContext, useContext } from 'react';

export interface __ContextName__Value {
}

const context = createContext<__ContextName__Value | null>(null);

export function __ContextName__Provider({ children }: __ContextName__Value & { children: React.ReactNode }) {
    return (
        <context.Provider value={{ }}>
            {children}
        </context.Provider>
    );
}

export function use__ContextName__(): __ContextName__Value {
    const value = useContext(context);
    
   if (!value) {
        throw new Error('use__ContextName__ must be used within a __ContextName__Provider');
    }

    return value;
}

Good job on the extension!
Curious to know if there a way for us to use only JS instead of JSX ?
PR's are welcomed, if so Il create one for it

Hi, I'm very interested in using your extension. However, when I try to to create a component, I get three errors saying something went wrong creating... one for each file. Do you have any idea of why this is happening? thank you.

Current behaviour

Props is the name of the props interface. e.g. ComponentAProps

Suggestion

I think it would be nicer if the component interface matches the component name. Maybe that can be a config option?

Current behaviour

When first starting the project I separated unit test from integration tests. The original thinking behind this was so that I could run tests quickly without having to spin up an instance of vscode.

This means I had to DI the VSCode window to functions so I could mock it out in the tests.

In hindsight this was dumb.

Suggestion

Use the default and recommended way of testing, which is integration test spinning up a special VSCode window.

https://code.visualstudio.com/api/working-with-extensions/testing-extension

Hi! 👋

I really enjoy the extension, but I can't set the fileExtension in VSCode to 'withoutX'.
There is no setting for it in the default Settings.json, and when I add it in the custom Settings.json it doesn't change the extension of the created files (see the second screenshot, where the line is greyed out). It still generates the .jsx files.

Would you know what the problem is?

Kind regards and thank you for your OS work,

Aiden

I'm not sure if you are still working on this, but a "simple" mode that only generates the component file itself would be nice

Current behaviour

After creating a module, I have to run prettier manually to make sure the files are formatted like the rest of the project :(

Suggestion

Add an option to run command/s on the files after they are created

e.g. create-react-component.afterCreatedHook: yarn prettier