Currently command-table.json include non-command info like folling
command name, command scope
file: which file to load when command invoked
So I will separate into two table. which I hope lead further faster pkg activation and reducing code complexity.
command-table.json: only include command info.
file-table.json: Manage which file operation class belongs. Used to lazy-require operation class.
Conclusion
After evaluation, I can't find notable activation performance boost.
Especially when user use Base.getClass in their init.js, it load files nevertheless on startup.
But I'll keep this time code separation because it reduce code complexity.
Currently
command-table.jsoninclude non-command info like follingSo I will separate into two table. which I hope lead further faster pkg activation and reducing code complexity.
command-table.json: only include command info.file-table.json: Manage which file operation class belongs. Used to lazy-require operation class.Conclusion
After evaluation, I can't find notable activation performance boost. Especially when user use
Base.getClassin theirinit.js, it load files nevertheless on startup.But I'll keep this time code separation because it reduce code complexity.