Closed taylorchasewhite closed 1 year ago
@chrissainty If this is as straightforward as returning that (presumably) inadvertently removed logic, I'd be happy to take a stab at it and open a PR!
Also ran into this tonight using the latest version.
@JeremySayers, I decided to go ahead and stick with updating my packages. To get around this issue until #222 gets merged in I just added more specific styles to the default classes applied. Here are the class names:
.blazored-toast-warning
.blazored-toast-info
.blazored-toast-error
.blazored-toast-success
Describe the bug Using the
WarningClass
,InfoClass
,ErrorClass
, andSuccessClass
no longer applies the specified classes to the toast.To Reproduce Steps to reproduce the behavior:
BlazoredToasts
is consumed), use custom classes for your toasts:Expected behavior Append the specified string in
WarningClass
(and others) to the rendered BlazoredToast component's class list (e.g. apply to ToastSettings object).Hosting Model (is this issue happening with a certain hosting model?): All hosting models.
Additional context It looks like this happened in #181 in commit 2a3eaa4 where we changed the ToastSettings initializer to be multi-line, the additional class logic was dropped.