question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

prompt: reimplement with ink

See original GitHub issue

The current implementation of @commitlint/prompt is tied to vorpal.

While vorpal provides great UX in a lot of ways it limits the adaptability of @commitlint/prompt in important ways, e.g. #46, #63.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:1
  • Comments:12 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
curly210102commented, May 2, 2021

@beetcb Glad you has the same needs and also taken actions.

It is unlikely to merge code directly, I think the point is that these two implementations are from different motivation.

cz-commitlint vs @commitlint/prompt

The motivation of cz-commitlint is to provide commitizen adapter, help commitizen works with commitlint.config.js. cz-commitlint replaces the role of @commitlint/prompt. I think users who try to use @commitlint/prompt in combination with commitizen(instead of using @commitlint/prompt-cli), want to benefit by commitizen’s good interaction and commitlint configuration. But @commitlint/prompt using vorpal instead of inquirer, so the combination is meaningless. cz-commitlint is work for this, based on inquirer, friendlier to commitizen users.

commitlive vs @commitlint/prompt-cli

commitlive is an independent commit tool, provides interactive CLI and message committer. The motivation is same with @commitlint/prompt-cli. We need a commit tool which is good enough to replace commitizen + cz-commitlint. And commitlive has taken the first step, I think there is one thing need to be considered firstly: the reasons to use repll instead of inquirer.

2reactions
marioneblcommented, Feb 6, 2020

i started looking into this and Ink seems nice, but using react to create cli seems like overkill to me

I beg to differ in this case - prompt has a lot of in-place updates based on a central state so it is well suited for implementation via an immediate mode UI pattern (such as React).

Do you have a different approach in mind?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Building a Terminal Wordle Game with React Ink - Atomic Spin
I recently decided to write my own Terminal Wordle and used Ink, a library that lets you build Terminal UI apps using the...
Read more >
commitlint - Bountysource
I'm trying to commit in a new repository that uses husky and my commit should work and pass husky checks as expected. Current...
Read more >
papertty - PyPI
PaperTTY is a simple Python module for using affordable SPI e-ink displays as a computer monitor, with a Raspberry Pi being the typical...
Read more >
CBGP on Twitter: "#ResearchCBGP | Real‐life evaluation of ...
Real‐life evaluation of molecular multiplex IgE test methods in the diagnosis of pollen associated... This study compared two molecular tests, ISAC and ALEX2, ......
Read more >
Inktober Art Challenges Invite You To Draw Every Day in ...
Inktober : The Worldwide Art Challenge That Has Everyone Drawing in ... Starting in 2016, Inktober has had an official prompt list with...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found