Loris Bettazza
Loris Bettazza
@speshak I'm more leaning towards the second option, this should be done externally to the library. Also while the format looks like markdown, it's not exactly a common flavour of...
The marked library seems relatively easy to extend, I got bold to work, but the new problem is that newlines are not normally respected since markdown needs 2 spaces at...
We had some discussion for this sort of thing here, feel free to give it a read: https://github.com/Pustur/whatsapp-chat-parser/issues/251 I think this feature is cool to have, but i don't want...
This is a duplicate of https://github.com/Pustur/whatsapp-chat-parser/issues/261 I don't know when i'll be able to fix it
@wasi2gh You could have a look at https://github.com/Pustur/whatsapp-chat-parser/blob/master/src/parser.ts
Hi @Rahmican, For the participants you could already get that information by doing the following: ```js const messages = wcp.parseString(chatLog); const participants = new Set(messages.map(m => m.author)); console.log(participants); // Set(5)...
@Rahmican This issue is blocked by #258, once that is resolved I can go ahead an release a new major version that changes the output as shown above. The problem...
Historically system messages did not have an author, but now it seems like new exports follow some new rules: - In a 1 to 1 chat, the system messages are...
@gitkps Have you checked #32? Maybe it's the same issue.
ctrl + F is not enough?