nostackapp / ns-flip Goto Github PK

Is your feature request related to a problem? Please describe.
There is a bit of a learning code for setting up a template. You have to understand

1. how to modify the ns file
2. specifically what static types exist and what they require in their specs for the template.
3. (more trivially) the need to update the generated code with "ns generate".

Currently, the only way to do 2 is by looking at the README for the template. That's not something that will always be uptodate, if done at all, and it can easily have omissions.

Describe the solution you'd like
It would be much nicer if we could instead have a command like ns settings that prompts the user for whatever is needed to customize the instances. That way, they wouldn't need to learn 1 or 2 at all, and could even be prompted for 3. (In fact, regeneration could be done automatically.)

I think that the best solution would be

1. modify the config (unfortunately, a breaking change) to add specs for each static type. Also description.
2. create a command that prompts for creation of each thing in the spec. Then the template user will just fill them in and the ns file will be generated from it.

Is your feature request related to a problem? Please describe.
The newtemplate prompts for preCommands are confusing, and also there's no confirmation when you are done.

Describe the solution you'd like
A nice bullet-pointed explanation of types of preCommands, and some sort of confirmation message.

While $appDir works fine for preCommands, it doesn't work for interactive. There's no reason why it shouldn't be used for both.

Describe the bug
no help option for newtemplate command

To Reproduce
Steps to reproduce the behavior:
call ns newtemplate -h

Expected behavior
should display help for the command

It's a pain to wrap ns delimiters inside of comment delimiters for other languages like markup.

Describe the bug
When a template has no helpers directory the generation fails

To Reproduce
Steps to reproduce the behavior:

1. create a template with no helpers file
2. generate.

Expected behavior
Should generate without helpers

It is very easy to forget to insert a {{nsFile}} at the beginning of a file template, and can really cause problems. It should be automatically generated.

the current wiki needs to have a concrete set of steps for how to convert an app insto a template.

Custom code is not properly updating. Seems to be a problem with the insertion of custom code expecting a location and not finding it.

Even though a cloned version works fine, the installed version is claiming "SyntaxError: Cannot use import statement outside a module" when running 'test'.

Should add testing for errors e.g. no code base specified.

Describe the bug
When a template is installed into npm global, the context there prevents the init file from working.

To Reproduce
install easy oclif cli using npx. Will state that a colon for a parameter type is faulty.

Expected behavior
should properly generate.

The code is still only filtering for js, jsx and md files when saving custom code. Ignores what's in the template.

Currently, having a starter and a code base is not sufficient for test, because if you don't have the template locally the config info is not getting copied over.

It seems to me that the best solution is to copy the config over to a starter in newstarter, and then from the starter to the code base in newcode or regenerate. Then test will grab it from the config file directly.

When following the instructions to create a template, you'll get an error:

  ✔ Execute Pre-Commands
  ✔ Install General Packages...
  ✔ Install Dev Packages...
  ✖ Add Meta-Data
    → Cannot set property 'starter' of undefined
    TypeError: Cannot set property 'starter' of undefined

That's because appInfo is undefined.

When a command accepts an unlimited number of arguments and throws an error if one is not recognized, the redirection (">>") to the log file is creating a problem.

Is your feature request related to a problem? Please describe.
It's very easy to forget to regenerate after updating settings. That is very frustrating.

Describe the solution you'd like
To have a prompt to offer to generate, and then do so. But it shouldn't be the default, because currently generation does not check first.

Describe the bug
If you run with a template that contains packages, e.g. for the init.ts file, the packages will not be found unless they happen to belong to ns-flip

To Reproduce
Steps to reproduce the behavior:

1. run npx easy-oclif-cli $CODE_DIR
2. See error git-user-info will not be found

Describe the bug
calling ns newtemplate is generating sample code with the name $CODE..sample instead of $CODE.sample

Must add a directory copy into the regenerate sequence.

Describe the bug
When you select a static instance named "add" in the settings command menu, it instead prompts to add a new instance instead of to edit the add instance.

To Reproduce
Steps to reproduce the behavior:

1. call ns settings
2. get to the menu for a specific static type "X"
3. select Add New Instance of X
4. call it add
5. select 'add'

Expected behavior
Should be opening the menu to modify add