[FIX] Attachment timestamp from and to Apps system not working #12445
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rodrigok
approved these changes
Oct 27, 2018
Merged
|
@rodrigok @graywolf336 I have a feeling that this PR caused new issue. Now when integration doesnt forward timestamp, then 1 January, 1970 0:00 is shown for attachment. |
|
Interesting, that shouldn't happen. Do you have any steps to reproduce this easily? |
|
@graywolf336 Same happening here when sending messages through API without ts set. |
|
Is this going to be repaired? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Rocket.Chat system expects a string for the
tsproperty of attachments and the Apps system expects aDateobject. This fixes that to ensure the two work well with each other.