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

[Spike] Yeoman vs inquirer+ejs #1187

Closed
3 tasks
dhmlau opened this issue Mar 26, 2018 · 4 comments
Closed
3 tasks

[Spike] Yeoman vs inquirer+ejs #1187

dhmlau opened this issue Mar 26, 2018 · 4 comments

Comments

@dhmlau
Copy link
Member

dhmlau commented Mar 26, 2018

Original issue: #844
The outcome of the discussion was to create a spike:

  • Verify the pain points that @bajtos has listed and see there are fixes/solutions without abandoning Yeoman.
  • Identify what's needed to build our CLIs using inquirer and ejs directly.
  • Build a PoC for a simple generator such as app.
@dhmlau
Copy link
Member Author

dhmlau commented Jun 19, 2019

With more CLI commands using Yeoman at this point, I'm not sure if it worths the effort to look into other alternatives to replace Yeoman. I'd like to close this issue because it won't be our focus in near and mid term to get to this. What do you think, @strongloop/loopback-maintainers?

@bajtos
Copy link
Member

bajtos commented Jun 21, 2019

-1

The issue #844 lists at least 8 pain points that are still relevant. Every new CLI command added in the current Yeoman style is inflating the tech debt we have in our CLI.

I think we should instead prioritize this spike higher in our backlog, e.g. for 2019Q3.

@stale
Copy link

stale bot commented Jun 15, 2020

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Jun 15, 2020
@stale
Copy link

stale bot commented Jul 18, 2020

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Jul 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants