[Feature request] Use the most up-to-date user information available

[mlomb]

[Feature request] Use the most up-to-date user information available

[mlomb]

Probably this line:

chat-analytics/pipeline/parse/parsers/DiscordParser.ts

Line 61 in cb2e618

const name = message.author.nickname || message.author.name;

In older exports nickname is not available but name is

[HopperElec]

Ah yes, that would be it!

…

On Thu, 19 Jan 2023 at 02:11, Martín Lombardo ***@***.***> wrote: Probably this line: https://github.com/mlomb/chat-analytics/blob/cb2e61898e6d2a6e1cde43e64fa4f2f93826f92f/pipeline/parse/parsers/DiscordParser.ts#L61 In older exports nickname is not available but name is — Reply to this email directly, view it on GitHub <#44 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMPUIAQRU2PZQ346XD4LO33WTCPDJANCNFSM6AAAAAAT7Y4FM4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[mlomb]

About to up-to-date information, it used to keep the most up to date info but that required overwriting the object every time, so I just kept the first
How could it be done without checking every field? (every time we find an author in a message)

[HopperElec]

Relating back to this comment, I think this would be another thing improved using hashing, as you could choose to only update the user if the same object can’t be found in the list of users. Of course, this would require re-parsing all the user information for every message, so it might be a good idea to produce the hash using the raw data provided in the export instead of the parsed data.