You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current JS codebase relies on script tags, leading to global scope pollution. I recommend refactoring to ES6 modules for better organization and encapsulation. Additionally, adding JSDocs for basic types can enhance code documentation.
The text was updated successfully, but these errors were encountered:
Sure, let's do that. I'm happy to move to modules as they seem reasonably well supported. However I don't want to add node.js as it would make it harder to get started on the project.
JSDoc doesn't need Node.js and serves as a great alternative to TypeScript.
It enhances code documentation without introducing the complexities associated with TypeScript.
I am avoiding TypeScript for the same reason (to keep this project beginner friendly).
JSDocs are optional comments above functions, providing a way to document code by specifying the function's parameters, return types, and other relevant details.
Check here : https://jsdoc.app/about-getting-started
I'll initiate the development of a plan outlining the steps for transitioning to modules. Let's discuss the plan here before proceeding with the coding phase!
The current JS codebase relies on script tags, leading to global scope pollution. I recommend refactoring to ES6 modules for better organization and encapsulation. Additionally, adding JSDocs for basic types can enhance code documentation.
The text was updated successfully, but these errors were encountered: