dest as argument about agrippa HOT 4 CLOSED

Great!

I've just release the first RC for v1.1.0, and this feature is part of it! Check it out in the release page. Please update me if you find any bugs, or have anything to suggest.

from agrippa.

Hi!
I totally agree with you - I've been missing this feature myself, and adding a --dest flag (or something equivalent) is the main feature I'm planning for v1.1.
I'm hoping to complete it in a few days.

As a workaround until then, you could cd into ./src/components in a new terminal, and call commands from there. It's not perfect, but I'm hoping it'll be good enough to get by until it's implemented.

Thanks for reaching out!

from agrippa.

In rough terms, what I want to add is this:

• a --componentDir flag for setting a base component folder; this is equivalent to ./src/components in your example.
  I'm assuming most projects have some sort of such a base folder, which most components would be created in (either as direct children or nested in more folders).
• If the user wants to create a component in a folder relative to the componentDir, instead of the directory itself, they can use a '--dest' flag with a relative path (in addition to componentDir), e.g. agrippa gen top-bar --componentDir ./src/components --dest ./common would generate the component in ./src/components/common.
• An alternative to using dest would be to input a relative path for the component name - which functionally should give the same result.
  For exmaple, agrippa gen --componentDir ./common/top-bar ./src/components should give the same result as agrippa gen top-bar --componentDir ./src/components --dest ./common.

In a typical project, componentDir would be defined in the config, and the --dest flag (or a relative path as the name) would be used to append to that through the CLI when generating the components themselves.

Nothing here is final (especially the naming), but I think this is a good solution for the different major use-cases of this feature.

What do you think?

from agrippa.

In rough terms, what I want to add is this:

• a --componentDir flag for setting a base component folder; this is equivalent to ./src/components in your example.
  I'm assuming most projects have some sort of such a base folder, which most components would be created in (either as direct children or nested in more folders).
• If the user wants to create a component in a folder relative to the componentDir, instead of the directory itself, they can use a '--dest' flag with a relative path (in addition to componentDir), e.g. agrippa gen top-bar --componentDir ./src/components --dest ./common would generate the component in ./src/components/common.
• An alternative to using dest would be to input a relative path for the component name - which functionally should give the same result.
  For exmaple, agrippa gen --componentDir ./common/top-bar ./src/components should give the same result as agrippa gen top-bar --componentDir ./src/components --dest ./common.

In a typical project, componentDir would be defined in the config, and the --dest flag (or a relative path as the name) would be used to append to that through the CLI when generating the components themselves.

Nothing here is final (especially the naming), but I think this is a good solution for the different major use-cases of this feature.

What do you think?

I think it will be useful. The componentDir flag is for agrippa.config.js and --dest is optional will be good.
CLI command will be short by this for eg agrippa gen component-name --componentDir [get automatically from agrippa.config.js | ./src/components] [--dest ./common | null]

from agrippa.