Timeline for Handle multiple Toast Messages coming from various LWCs in a page
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 1, 2023 at 19:40 | comment | added | sfdcfox♦ | @HenryJones The docs include a bit about system messages. Inline errors are probably more appropriate for most regular types of automated actions that end abnormally. Like I said, I'd suggest reading the docs and understanding recommendations. A common messaging system might not make sense to a user, since it won't be easy to identify those problems. Maybe consider investing in a logging framework, instead. | |
| Jul 1, 2023 at 19:23 | comment | added | Henry Jones | Yeah so basically each component calls a method in Apex which may or may not end with an error. Depending on different scenarios, multiple server-side errors are thrown and with the current implementation, they are displayed using a simple Toast Message in each LWC. There is not the case for not filling out required fields and so on, we are just looking for a better handling of this errors for this use cases and we thought that building a separate lwc like an error-aggregator component and using a <template> tag would be useful in this case but this is just an opinion. | |
| Jul 1, 2023 at 18:50 | history | answered | sfdcfox♦ | CC BY-SA 4.0 |