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
I think it makes sense to spend some time migrating asciimath's core functionality to a modern and more modular build system. I was thinking something like rollup. I find myself often requiring only a subset of asciimath's core functionality, and it would be super cool to be able to include only that functionality when I need it.
For example, I recently needed to convert asciimath markup to latex, which requires finding the right file (which has a large amount of duplicated code), and then using that file. It would be great to modularise this codebase for two main reasons:
It makes it much less intimidating to new contributors who might like to use it
It makes the intent of different code sections clearer
It makes it easier to integrate asciimath into your workflow
Any thoughts?
The text was updated successfully, but these errors were encountered:
Yep, I agree that a dist folder would be necessary. I'm really only advocating for a refactor. It would make using asciimath easier if you only need some of the functionality. It also eliminates the code duplication that we have across the multiple files.
I think it makes sense to spend some time migrating asciimath's core functionality to a modern and more modular build system. I was thinking something like rollup. I find myself often requiring only a subset of asciimath's core functionality, and it would be super cool to be able to include only that functionality when I need it.
For example, I recently needed to convert asciimath markup to latex, which requires finding the right file (which has a large amount of duplicated code), and then using that file. It would be great to modularise this codebase for two main reasons:
Any thoughts?
The text was updated successfully, but these errors were encountered: