Contribute and Learn!

[mukuljainx]

When I was writing Mokku, I tried my best to keep it clean, I guess I kept it as per my previous knowledge and standards. To be honest, there is a lot of scope for improvement, if anyone is interested in helping me please comment. I will add tasks in the next comments.

What you will get:

1. If you are new to react, hands-on experience on the mid-sized project.
2. Learn how to write an extension.
3. Communication between different parts.
4. React Hooks
5. Learn to write a clean code (by cleaning it 😅 )

I will be guiding you throughout each task.

[Julioevm]

I think I would like to help out, I've been using the extension and find it quite useful. And I work with React so maybe theres something I can contribute with, as far as find the time for it 😅

[mukuljainx]

Hi @Julioevm, Thanks for showing interest!

There are 2 things you can pick!

1. After duplication of request last in the list does not work #69 seems like a good starting point!

You can visit this file for mock interface (don't worry if don't know TS):
src/interface/mock.ts

Store: src/services/store/index.ts
All the input output to DB happens through this file and while toggling something wrong is here!

Rest I am leaving you to explore, let me know if you need more insight.

---

2. React Panel app
   The component is entry point for Panel (the one you see in devtools) but the code is way to complicated! React component wise things are stable now but still needs refactoring! Though just keep in mind new v2 is on the way which will replace this all together!

[Julioevm]

Cool, I'll take a look!

[metin1]

Hi, @mukuljainx I use your extension. It's very useful. I want to contribute this project.

[mukuljainx]

Hi @metin1 , thankyou for your support! Unfortunately I am closing mokku (along with V2) for any further development.
It pretty useful but at the ends it injects a script in browser which can be very easily overwritten or break the app. Till Chrome support native reading and writing hooks there will be no development.

Chrome ticket API response reading: https://bugs.chromium.org/p/chromium/issues/detail?id=487422#c54