Files have large scope and broad categories, making it difficult to navigate, find, and read code
Ideal solution
Break the files up by feature most likely, so related code can go together and files can be more focused on something specific
Look for opportunities to rename things to be less confusing. Right now there are multiple paths to the same outcome, but we should funnel code paths through the same functions for consistency with checks and to simplify the code.
API should be clear (public net events, exports), which smaller file sizes contribute to. Backwards compatible API endpoints should be commented as such and marked deprecated.
It seems like there are abstractions that may make the code harder to navigate without adding value. Right now we have files that are collection of functions, which isn't specific enough to be useful.
The problem
Files have large scope and broad categories, making it difficult to navigate, find, and read code
Ideal solution
Alternative solutions
No response
Additional context
No response