search

tamhinsf / ChannelSurf

Move from Slack to Microsoft Teams and manage your Teams environment
114 stars 31 forks source link

Message order #27

Open JanisE opened 4 years ago

JanisE commented 4 years ago

I imported one rather small channel and I'm looking at the HTML file of messages compilation ChannelSurf created for me. The message order is a mess...

The first message is from the 18th of February which is more than half in the whole discussion history. The messages are displayed successively until 4th of March (which is not the last day of messages), then jumps back to 21st of January. Then, after a few messages, jumps to the 27th of February (and, no, it's not the same thread). Then again, back to the 7th of February, and then back to the 15th of January which, at last, is the actual first messages of the channel history.

And after that, the jumping goes on and on. And it's not explainable by threads. Although, another issue – which would be a new feature request, I guess – is that the threads are not distinguishable visually, in the imported compiled HTML. All the messages are listed in one, plain list.

The content export ZIP from Slack contains the JSON files named by the dates, and they seem sorted correctly. So, there is nothing there for me to fix, it's ChannelSurf that mixes all the dates.

JanisE commented 4 years ago

OK, so I found the source message JSONs were not being explicitly sorted when reading the message data. And apparently in most cases the order was as expected (as no one else has complained), but for me (I'm using Linux, maybe that's related) the order was wrong.

Created a pull request to fix this issue.