Removal of PriceWatcherService #121
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following changes:
PriceDropController
is now part of theProductsService
. I introduced a simple unit of work and async factory that encapsulate ADO.NET for SQL Server and In-Memory data. This allows access to the database in a completely asynchronous manner while keeping the business logic in the controller completely decoupled from any specific data access technology.PriceDropController
.PriceWatcherController
with itsRegister
endpoint to the PriceDropNotifier service. It currently uses an in-memory data access layer with a simplified Unit-of-Work pattern to store registrations.PriceDropNotifierController
now fetches all registrations and sends emails accordingly.Issues I still have: