Last Harvest Date Tracking for Asset Retrieval #357
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.
Pull Request Description
This pull request introduces a new feature to enhance the asset retrieval process within our application. The changes made in this PR are as follows:
1. campaign.controller.js:
Added a new variable called
lastHarvestDate
tocontrollers/campaign.controller.js
.Implemented an update operation for the
CampaignLink
model usingawait CampaignLink.updateOne()
. This update operation sets thelastHarvestDate
field to the value ofprom.lastHarvest
when a user retrieves assets.Sample code snippet:
await CampaignLink.updateOne({ id_prom: idProm }, { $set: { lastHarvestDate: prom.lastHarvest } });
2. campaignLink.model.js:
lastHarvestDate
of typeNumber
to themodel/campaignLink.model.js
.These changes aim to provide valuable functionality for tracking and managing the last harvest date of assets, which can be beneficial for various aspects of our application. Please review the code and provide feedback as necessary. Thank you!