I wish #Haskell had an interactive command-line application library like #Deno's #Cliffy.
Conversation
Notices
-
Embed this notice
洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Wednesday, 04-Oct-2023 08:34:53 JST 洪 民憙 (Hong Minhee)
-
Embed this notice
glyn (underlap@fosstodon.org)'s status on Wednesday, 04-Oct-2023 17:55:00 JST glyn
@hongminhee What does Cliffy provide that optparse-applicative doesn't? Presumably some kind of interactive code generation.
-
Embed this notice
洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Wednesday, 04-Oct-2023 17:55:00 JST 洪 民憙 (Hong Minhee)
@underlap For me, the lack of prompts is the biggest miss, though I find it not to be something applicative-optparse should have. I'd like to see a library that deals with prompts well. The one that comes closest is fortytwo, but it seemingly doesn't support Windows.
-
Embed this notice
洪 民憙 (Hong Minhee) (hongminhee@todon.eu)'s status on Wednesday, 04-Oct-2023 19:28:02 JST 洪 民憙 (Hong Minhee)
@underlap A separate library seems like a better idea. IMHO prompting the user for input in itself seems independent of parsing command line arguments.
-
Embed this notice
glyn (underlap@fosstodon.org)'s status on Wednesday, 04-Oct-2023 19:28:03 JST glyn
@hongminhee Would it make sense to create a separate prompt helper library, possibly designed for use with optparse-applicative? What do you think?
-
Embed this notice
glyn (underlap@fosstodon.org)'s status on Wednesday, 04-Oct-2023 19:29:35 JST glyn
@hongminhee E.g. are you talking about simply prompting the user for input, or displaying certain information in a prompt, or what exactly?
-
Embed this notice
glyn (underlap@fosstodon.org)'s status on Wednesday, 04-Oct-2023 19:29:36 JST glyn
@hongminhee Either way, it would be good to clarify your prompt requirements, so someone else could help provide that feature.
-
Embed this notice