Conversation
🦋 Changeset detectedLatest commit: b245c9b The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
|
Do we need the same hint if you run |
|
this change is already shared with |
benmccann
left a comment
There was a problem hiding this comment.
Oh, that's pretty weird. You'd want it to show up in the first create question - not the third
|
it only shows up on the multi-select where there's a difference between |
|
I thought about that and figured that it's fine to exclude it from succeeding* multi-select prompts as you've been "taught" what to do by the time you reach this prompt |
Not necessarily, because you can just run |
|
What is the reason for not adding hints to subsequent multi-selects? Is it because of clutter? Isn't it always better to provide visual aid, I understand it's squares for multi-select and circles for single-select. But I find that hardly noticeable. |
|
I'd have to see what it looks like, but my first reaction is that it'd be too noisy and we should mention it only once |
|
seeing it now, I still think it adds unnecessary noise. this noisiness is also exacerbated when the instructions are kept on screen long after prompt submission |
|
Is it possible to add a check to only show the hint on the first multi-select the user encounters, or would that increase the code complexity. If possible, this would reduce clutter and still have hints regardless of which branch the user takes. |
This reverts commit 407d856.
|
Let's only add this to the integration-selection question for now, as everyone seems to agree there. Let's get this merged and hear for user feedback |


related conversation
https://discord.com/channels/457912077277855764/1298479734606528628