Enhance Error Logging and Address Minor TODOs #6538
Description
Is your feature request related to a problem? Please describe.
While working with the Hubs codebase, I noticed several areas where silent failures occur (e.g., empty .catch blocks) and a number of TODO comments indicating pending improvements. These can make debugging more difficult, especially for new contributors or when tracking down unexpected behavior. Improving developer logs and addressing minor TODOs would enhance maintainability and overall developer experience (DX).
Describe the solution you'd like
- Add helpful
console.warnorconsole.errormessages in places where failures are currently silent, particularly in.catchblocks. - Gradually address simple
TODOitems that can be resolved without large architectural changes. - Ensure consistent logging practices across the codebase to make debugging easier for both core developers and open-source contributors.
Describe alternatives you've considered
- Leaving the current logging as-is, but this risks continued confusion when debugging.
- Creating separate issues for each
TODO, but many are minor enough to be handled collectively under a broader developer experience improvement initiative.
Additional context
- Found multiple silent
.catchblocks during a grep search that could benefit from at least basic warnings or error outputs. - Several
TODOcomments are low-hanging fruit and could be cleaned up to reduce technical debt. - This improvement aligns with open-source best practices by making the project more approachable for contributors.
Example:
promiseFunction()
.catch(() => {
// Silent failure — could log context here
});Would become:
promiseFunction()
.catch((err) => {
console.warn("Promise failed in [function/module]:", err);
});These small changes can significantly improve traceability during development.