Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Class Alert doesn't store any provided information #11

Open
Byloth opened this issue Jul 21, 2024 · 0 comments
Open

Class Alert doesn't store any provided information #11

Byloth opened this issue Jul 21, 2024 · 0 comments

Comments

@Byloth
Copy link
Owner

Byloth commented Jul 21, 2024

As briefly described in the Issue #9, Vuert allows the developer to extend the options provided (among the default ones) when emitting a new alert.
Or, at least, it should do so... In reality, it isn't like that.

In the constructor of the Alert class, the options are -indeed- selected one by one and assigned to the Alert object.
What happens if the developer adds some new properties? They're simply ignored and lost.

Should it just use the payload property that accepts any kind of data?
What if I want to provide some data to the AlertHandler but not to any eventual custom child component?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant