You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The thing is that there is the initial currently. But i believe it would be better the initial to be set in parens before the ›. It's cool feature, and it can be used to set default values, but if user dont want the default he need to waste time in deleting it to set another. As about if we have default then it can be shown in parens same as initial (if initial not set) and if user like the default then just to click enter.
One more thing that i'm thinking about is required boolean prop to allow the question to be required or not. If required and not set then throw, end the stream or show message which is kinda related to the discussion in #2 (comment) thread.
If not adding required then validate is good option too. Use case.
The text was updated successfully, but these errors were encountered:
I'll consider adding some visual feedback for initial values but it's very low priority at the moment. Fixing bugs and writing tests is the main focus now. I'll close this for now.
Heya! ✋
The thing is that there is the
initial
currently. But i believe it would be better the initial to be set in parens before the›
. It's cool feature, and it can be used to set default values, but if user dont want the default he need to waste time in deleting it to set another. As about if we havedefault
then it can be shown inparens
same asinitial
(if initial not set) and if user like the default then just to clickenter
.One more thing that i'm thinking about is
required
boolean prop to allow the question to be required or not. If required and not set then throw, end the stream or show message which is kinda related to the discussion in #2 (comment) thread.If not adding
required
thenvalidate
is good option too. Use case.The text was updated successfully, but these errors were encountered: