Change Details

>Note: This is a open (placeholder) discussion ticket. Please do not assign it to yourself. Currently the Client-side (React) code of the tool is very lengthy and not dev friendly. We can look into refactoring all of the codebase, and try to remove all code-smells, unnecessary code .etc **Open Discussion** 1. Currently the client is ReactJs-based service (powered by Vite). We can look into migrating to VueJs at some point (to be more Wikimedia friendly). 2. If we stay on React, then should we consider TypeScript? It can be a good way to impose strict types and avoid code-smells. Although we're not really sure if its compliant with Wikimedia policies. If not lets try to impose JsDoc on almost every file (to make it dev friendly). Keeping the pointers and ticket open for a discussion. Post which we can start with implementation. This will be a long and continuous task, and hence is advised to break this task into smaller sub-tasks.

>Note: This is a open (placeholder) discussion ticket. Please do not assign it to yourself. Parent ticket for VCT Re-arch. Child tasks include UI/flow improvements, stabilizing current functionalities, adding new ones .etc

>Note: This is a open (placeholder) discussion ticket. Please do not assign it to yourself. Currently the Client-side (React) code of the tool is very lengthy and not dev friendly. We can look into refactoring all of the codebase, and try to remove all code-smells, unnecessary code .etc **Open Discussion** 1. Currently the client is ReactJs-based service (powered by Vite). We can look into migrating to VueJs at some point (to be more Wikimedia friendly). 2. If we stay on React, then should we consider TypeScript? It can be a good way to impose strict types and avoid code-smells. Although we're not really sure if its compliant with Wikimedia policies. If not lets try to impose JsDoc on almost every file (to make it dev friendly). Keeping the pointers and ticket open for a discussionParent ticket for VCT Re-arch. Post which we can start withChild tasks include UI/flow implrovementation.ts, This will be a long and continuous taskstabilizing current functionalities, and hence is advised to break this task into smaller sub-tasks. adding new ones .etc