-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix interactive dialogs not showing #8427
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -22,6 +22,21 @@ function selectKeyboardType(type: InteractiveDialogElementType, subtype?: Intera | |
return selectKB(subtype); | ||
} | ||
|
||
function getStringValue(value: string | number | boolean | string[] | undefined): string | undefined { | ||
if (typeof value === 'string') { | ||
return value; | ||
} | ||
if (typeof value === 'number') { | ||
return value.toString(); | ||
} | ||
|
||
return undefined; | ||
} | ||
|
||
function getBooleanValue(value: string | number | boolean | string[] | undefined): boolean | undefined { | ||
return typeof value === 'boolean' ? value : undefined; | ||
} | ||
|
||
type Props = { | ||
displayName: string; | ||
name: string; | ||
|
@@ -34,7 +49,7 @@ type Props = { | |
dataSource?: string; | ||
optional?: boolean; | ||
options?: PostActionOption[]; | ||
value: string|number|boolean|string[]; | ||
value?: string|number|boolean|string[]; | ||
onChange: (name: string, value: string|number|boolean|string[]) => void; | ||
} | ||
function DialogElement({ | ||
|
@@ -59,7 +74,7 @@ function DialogElement({ | |
return; | ||
} | ||
onChange(name, newValue); | ||
}, [onChange, type, subtype]); | ||
}, [type, subtype, onChange, name]); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. for the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The idea is that |
||
|
||
const handleSelect = useCallback((newValue: DialogOption | undefined) => { | ||
if (!newValue) { | ||
|
@@ -68,7 +83,7 @@ function DialogElement({ | |
} | ||
|
||
onChange(name, newValue.value); | ||
}, [onChange]); | ||
}, [name, onChange]); | ||
|
||
switch (type) { | ||
case 'text': | ||
|
@@ -77,7 +92,7 @@ function DialogElement({ | |
<TextSetting | ||
label={displayName} | ||
maxLength={maxLength || (type === 'text' ? TEXT_DEFAULT_MAX_LENGTH : TEXTAREA_DEFAULT_MAX_LENGTH)} | ||
value={value as string} | ||
value={getStringValue(value)} | ||
placeholder={placeholder} | ||
helpText={helpText} | ||
errorText={errorText} | ||
|
@@ -102,7 +117,7 @@ function DialogElement({ | |
errorText={errorText} | ||
placeholder={placeholder} | ||
showRequiredAsterisk={true} | ||
selected={value as string} | ||
selected={getStringValue(value)} | ||
roundedBorders={false} | ||
testID={testID} | ||
/> | ||
|
@@ -116,14 +131,14 @@ function DialogElement({ | |
options={options} | ||
onChange={handleChange} | ||
testID={testID} | ||
value={value as string} | ||
value={getStringValue(value)} | ||
/> | ||
); | ||
case 'bool': | ||
return ( | ||
<BoolSetting | ||
label={displayName} | ||
value={value as boolean} | ||
value={getBooleanValue(value)} | ||
placeholder={placeholder} | ||
helpText={helpText} | ||
errorText={errorText} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any value (heh, pun intended) in converting
false
to string and gets "false"?I was thinking of option "true" / "false", but I have a feeling this gets converted somewhere already.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe if I understand correctly, the initValues function would have converted that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True/false values should only be used on Boolean settings, and those will use the
getBooleanValue
. If a boolean value gets into this point, probably is because something is "wrong", andundefined
is the safe approach.But I don't have a strong opinion on this. Nevertheless, it "should never happen".
Regarding the change to
getStringValue
, I would argue the argument is not optional. You must provide an argument, just that that argument can be undefined. 0/5 on that too, so if you have a strong opinion, happy to change it.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking of consistency. Since if people can pass undefined, it's almost like not
passing anything. But it is silly to see
getStringValue()
. I rather see people sendgetStringValue(undefined)
instead ofgetStringValue()
.Long to short: don't change. :P