useDialogs Make Payload a Node Rather than a String

[aress31]

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

[Janpot]

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?

[aress31]

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.

[github-actions]

This issue has been closed. If you have a similar problem but not exactly the same, please open a new issue.
Now, if you have additional information related to this issue or things that could help future readers, feel free to leave a comment.

Note

@aress31 How did we do? Your experience with our support team matters to us. If you have a moment, please share your thoughts in this short Support Satisfaction survey.