Missing `AutoDismiss` feature from the `BitMessage` component

[msynk]

Missing AutoDismiss feature from the BitMessage component:

• The BitMessage can utilize an AutoDismissTime parameter to implement such a useful feature

[github-actions]

Hello there! I'm a wiki 🤖.

Based on the content of this thread, I've found a potentially relevant wiki page for you!

✨ View Wiki Page

I hope this helps!

[nhwilly]

I tried this out and it's just what I needed.

In my case I need to conditionally auto dismiss the message. I don't understand the internals, but I did notice that changing my AutoDismissTime value during subsequent renderings didn't work as expected. In the end I ended up assigning a key to force it to work. Not sure if that's what was intended, but it's working this way.

My example code:

    string MessageKey => $"{State.ProviderName}:{State.CorrelationId}:{State.Status}:{State.Result?.Status}";

    TimeSpan? AutoDismissTime =>
        State?.Result?.Status is (ResultStatus.Ok or ResultStatus.Created or ResultStatus.NoContent)
        && State.Status is OpStatusType.Completed
            ? TimeSpan.FromSeconds(2)
            : null;

        <BitMessage @key="MessageKey" AutoDismissTime="AutoDismissTime" IconName="@Icon" Color="@Color" OnDismiss="OnDismiss" Multiline="@Multiline">
            <Content>
                @State.Message
                <ul style="margin:0; padding-left:1rem;">
                    @foreach (var validationError in State.Result?.ValidationErrors?.ToList() ?? [])
                    {
                        @validationError.ErrorMessage
                    }
                    @foreach (var error in State.Result?.Errors?.ToList() ?? [])
                    {
                        @error
                    }
                </ul>
            </Content>
        </BitMessage>

[msynk]

in our design, the BitMessage instance should not be re-used after dismissing. if you check our samples, you can see we are removing the component instance after dismissing, using an if statement. So, we only use the AutoDismissTime parameter on the first render, hence you can't utilize it by changing its value after render.

although, if you have any specific requirement on this matter, I suggest filing new issue since discussing it on a closed issue is not a proper approach.

[nhwilly]

Edit: I just wrote this on a closed issue. Exactly what you told me not to do.

🤦🏽

Thanks for that explanation.

I am using it in a modal to communicate status in the context of the modal and not the app in general.

So they'll get a "saving" message followed by a "saved" result, or errors, all shown with a message.

If the result is successful the message just auto dismisses.

It's working well by using the key approach I described. But is there a drawback to using the key? Like memory problems or other issues that will turn up later? Sometimes Blazor behavior is a bit hard to understand.

If not, this is fine and I won't file anything or make extra work.