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 dialog payload specifies that payload is expected to be of type string, which feels restrictive. For example, my use case involves passing a complex form as the payload. Expanding support to allow any type of payload would be highly beneficial.
Examples
No response
Motivation
Extending the usefulness of useDialogs.
Search keywords: payload useDialogs
The text was updated successfully, but these errors were encountered:
You should be able to pass anything as a payload. e.g. you can pass an object as we do internally for the system dialogs. The docs just use a string as an example. Perhaps we need to clarify this in the documentation?
I can confirm that it's possible to pass any payload, but the PropType in the example was somewhat unclear. It might be beneficial to include a note in the documentation to clearly state that any payload type is acceptable for the component, and to update the PropType from string to any.
Summary
The dialog payload specifies that payload is expected to be of type
string
, which feels restrictive. For example, my use case involves passing a complex form as the payload. Expanding support to allow any type of payload would be highly beneficial.Examples
No response
Motivation
Extending the usefulness of
useDialogs
.Search keywords: payload useDialogs
The text was updated successfully, but these errors were encountered: