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

feat: Add IToastService, IMesssageService, IDialogService to a new library Microsoft.FluentUI.AspNetCore.Components.Abstractions #1484

Open
davte-beijer opened this issue Feb 9, 2024 · 1 comment
Labels
status:needs-investigation Needs additional investigation vNext For the next major version

Comments

@davte-beijer
Copy link

davte-beijer commented Feb 9, 2024

🙋 Feature Request

I would like to use the following services: IToastService, IMesssageService, IDialogService without having to have a reference to the full Microsoft.FluentUI.AspNetCore.Components package, instead I would like to use something like Microsoft.FluentUI.AspNetCore.Components.Abstractions.

This would allows me to e.g. inject these services view models that are not in the same project as my Blazor UI code.

💁 Possible Solution

Microsoft.FluentUI.AspNetCore.Components package is separated into

  • Microsoft.FluentUI.AspNetCore.Components
  • Microsoft.FluentUI.AspNetCore.Components.Abstractions.

🔦 Context

If doing MVVM together with fluent-ui blazor, the simplest workaround is to put all view models inside razor.class lib or wherever the UI blazor components exists, however idealy I would prefer a finer level on granularity and separation between my view models and UI code.

@dvoituron
Copy link
Collaborator

This is indeed an improvement that could be useful in certain cases, like the one you're presenting.
It's not currently planned, but we can analyze it and put it in the backlog of a future major release.

@dvoituron dvoituron added the status:needs-investigation Needs additional investigation label Feb 9, 2024
@vnbaaij vnbaaij added the vNext For the next major version label Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:needs-investigation Needs additional investigation vNext For the next major version
Projects
None yet
Development

No branches or pull requests

3 participants