Submitting a new.arrayDoc change where the model has an onSave() function does not update the newValueModified in the change doc. So the change implemented does not include the onSave() modifications.
Found via new txtn on client. txtn model onSave had (removed) a txtnDate fixDate() function which modified the date. The fixDate() function DID run and returned the modified date but the newValueModified object was not updated with that updated date. Seems to be in mongoose-extend.
Confirmed this also occurs on replace.arrayDoc. See application (uscis) onSave() dateSubmitted, dateReceived. Dates are saved with local time rather than updated to :12:00:00z
Submitting a new.arrayDoc change where the model has an onSave() function does not update the newValueModified in the change doc. So the change implemented does not include the onSave() modifications.
Found via new txtn on client. txtn model onSave had (removed) a txtnDate fixDate() function which modified the date. The fixDate() function DID run and returned the modified date but the newValueModified object was not updated with that updated date. Seems to be in mongoose-extend.