javascript - In large JS apps where do I put custom methods to libraries and plugins -
I have a very large javascript application, which mostly use ZeeK and Knockout, basically I use my folder structure < There is a big isolation in code> app in which I have written and all the constants, views, models and views are divided into models. Then I have the seller , which is the code I do not write like jquery, knockout, plugins, etc. The problem is that where I keep the stuff which falls in the middle, I've written some custom binding for the noseout and some functionality of some jquery plugins has increased and they just got me in the root of my
app dir What is the best practice or naming convention for sitting?
+ app - constant - model - view-models - view jquery-plugin-extras.js knockout-binding.js etc + vendor Jquery.min.js knockout.min.js jquery-plugin .min.js
+ app - system (or core) // There is a core or system related generic-config / single location to store your configuration in, if you have only one, then put it on the root plugins / all plugins or bindings here - constellation - model - view-model S - Visual - Main.js // No Bootstrapping, initial configuration and go to this file. + Lib - jquery.min.js --knockout.min.js --jquery-plugin.min.js
Comments
Post a Comment