Closed infinite-persistence closed 3 years ago
Will give this a test soon, but this doesn't seem right as we always want to populate release time: "releaseTime will be undefined for new uploads."
releaseTime
and releaseTimeEdited
is only used in the GUI side to differentiate the following cases:
Ultimately, they get converted to the following when publishing:
if (releaseTimeEdited) {
publishPayload.release_time = releaseTimeEdited;
} else if (myClaimForUriEditing && myClaimForUriEditing.value.release_time) {
publishPayload.release_time = Number(myClaimForUri.value.release_time);
} else if (myClaimForUriEditing && myClaimForUriEditing.timestamp) {
publishPayload.release_time = Number(myClaimForUriEditing.timestamp);
} else {
publishPayload.release_time = Number(Math.round(Date.now() / 1000)); // new claim
}
So, release_time
will always be populated.
Gotcha...that makes more sense. Testing...
Issue
For
lbry-desktop #5514 - Add release date field
Changes
Updates for
UpdatePublishFormData
:releaseTime
is now a number instead of a string, matchingrelease_time
. It was getting confusing what the units were between the app variable vs claim variable.releaseTime
will always matchrelease_time
for an edit. It will be used in the GUI to reset just the date to the original, instead of having to reset the entire form.releaseTime
will be undefined for new uploads.releaseTimeEdited
will be used byupdatePublishForm
in the GUI to represent the desired new release time. Set toundefined
if we don't want to change the date.