Replacing the separating space between message and input

[jareware]

Really cool lib, love it!

Inquirer.js/packages/input/src/index.ts

Line 74 in 346cf16

return [`${prefix} ${message}${defaultStr} ${formattedValue}`, error];

Would it be somehow possible to customize the separator " " between defaultStr and formattedValue here? ☝️

I would like to format my prompts so that the result shows in the console as:

key=<value>

without any space between, but currently one can only achieve this:

key= <value>

with suffix: '='.

Thoughts?

[SBoudrias]

I'd like to get better theming support down the line; but I'm not sure what a good interface for this would be across prompts yet.

[jareware]

Would it make sense to have a separator prop, defaulting to " " to keep backwards compat, and support it wherever suffix is supported? Might be quite easy? 🤔

[Toldoven]

@SBoudrias #1323 Says it should fix this issue, but it's still relevant

It's because of this .join(' ')

Inquirer.js/packages/input/src/index.ts

Line 114 in 9b226bd

.join(' '),

return [
    [prefix, message, defaultStr, formattedValue]
      .filter((v) => v !== undefined)
      .join(' '), // Not configurable
    error,

Can we make it configurable?

[Toldoven]

My use case: I have an input where user enters a name for a new branch, but it already has a prefix that can't be changed:

E.g.

Branch Name: feature/<EDITABLE INPUT>

So, I'm setting Branch Name: feature/ as my message, but it results in this

Branch Name: feature/ <EDITABLE INPUT>

For this use case there's another potential solution: Add a new property for "Answer prefix" or something like this

[SBoudrias]

I'm open to adding a formatter function to the theme. Let's make sure it is applied consistently across prompts.