What is the best way to start contribuiting?

[ncesar]

Hey guys, I was curios to know how you guys are debugging WhatsApp to understand when there are new changes, here is a commit that shows a good example where WhatsApp updated the createGroup function: 79f55b6

I'm very interest so I can start contribuiting to the repo as well but I'm unsure on how to debug and find the new changes

[carlosmixz]

You can use the source tab on Chrome DevTools and start searching the functions that you want to debug with ctrl+shift+F, something like "vote_pool" or just "vote", then reading the wa-js source code to urderstand how to get an function with the exportModule and how to use the function with the debug tool. When you try the first or second time is very hard to understand, but with time you get it easy.

[KalaKala123]

@carlosmixz can you elaborate a little further?
I managed to fix this issue locally #2930 but i dont understand how to contribute a PR with the fix.

I used a method on WAWebChatForwardMessage module that is called forwardMessages and used it.
This is how the method is invoked

            let moduleToUse = whatsApp.webpack.modules((_, moduleId) => moduleId === "WAWebChatForwardMessage")

                moduleToUse .WAWebChatForwardMessage.forwardMessages({ chat: chat, msgs: [msg], multicast: false, includeCaption: false, appendedText: false });

This code works, but how do I add it to the library?

[carlosmixz]

You can see at #2960 how I can use your discovery to create a new function that works. Why a new function? Because the library needs to maintain support for older versions, and I can't patch the old function without breaking compatibility.

Breakdown (a littlebit):

1. Forked the repository
2. Clone on my local computer
3. Created a new branch with git checkout -b
4. Saw your code to export the correct module
5. Analysed the options to integrate with the main function without break the compatibility.
6. Created another function to use the new module.
7. Build and test.
8. Created the commit and the PR on GitHub.
9. Analysed and fixed the PR test errors.