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

Standard (Public interface) of ViewModel level services #6

Open
AlexeyTolstopyatov opened this issue Dec 19, 2024 · 0 comments
Open
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed question Further information is requested

Comments

@AlexeyTolstopyatov
Copy link
Owner

View-Modeling services standard

At the moment of 19.12/2024 Standard API of Application's services looks like this:

interface IOnionService{
  /// <summary>
  /// Contains the EntryPoint in Service. All arguments
  /// sets in Global fields and requires to work the service
  /// </summary>
  void OnionMain()
}

My suspicions about the wrong approach

for using DI principle I need to select the scope where all services are the same by themself structure of implementation.
But services contains same elements only in their start positions. Because for beginning scan or parse something needs to yield running Service from Task. Just because I decided to select EntryPoint of all Services, which View-Model ware uses.

@AlexeyTolstopyatov AlexeyTolstopyatov self-assigned this Dec 19, 2024
@AlexeyTolstopyatov AlexeyTolstopyatov added documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed question Further information is requested labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant