Investigate improved method of modularization about smk HOT 1 CLOSED

After time spent looking more closely at how SMK modules are built and loaded, we've decided not to take further steps toward changes in modularization at this time. Here are takeaways from our investigation.

• Unit testing - tests of specific units of code that do not require loading SMK - is simply not feasible given the current architecture.
• We agree that there’s usefulness to the strategy of putting testable code into a global object (SMK.UTIL or new SMK.x objects) and then testing it in an integration test tool like Cypress. Going forward, if we find a good use case for testing new code, we can consider implementing this strategy.
• It would be interesting to spend time building an “SMK 2.0” minimum viable product (for example, just loading a base map) using current best-of-breed methodologies. The MVP would also need to work with current SMK configuration. However, this would be a big undertaking, and is not planned for the near future.

from smk.