[AF-33] Set up the end of the auction #38
Merged
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.
Summary 🔴
Setting up the auction completion involves defining the parameters and conditions that govern the conclusion of bidding activities. We will involve the integration of a notification system (via email) to inform participants about the imminent conclusion of the auction.
Additionally, the configuration should enable post-auction procedures, such as invoicing and notifications to winners and participants. The version
0.8.6
CHANGELOG contains all the details.Proposed / Possible solution 🔴
standard
andclosed
auctions, where there is no change in the end date, we only use a simple scheduling in the background job.penny
auctions, the end date is updated with each new bid. Therefore, once created, a date is added (according to the timer), and it is updated again with each new bid. Finalization is also done using a background job. To avoid conflicts with lots of unnecessary bidding and scheduling, we use sidekiq unique jobs to manage this.