Score Breakdown

Problematic Comments

Each problematic comment (i.e. comments with TODO, HACK or FIXME in it) contributes -100 points to the health score.

• // TODO: should we throw if this cannot be found? Alternatively / in addition, if calls below to complete* APIs fail, maybe we should throw then?
• // TODO: in the future, if we add more of this kind of logging, then perhaps worth considering moving to a structured logger with different log levels
• // TODO: we should move to Deno.serveonce it is stable instead ofDeno.serveHttp() https://docs.deno.com/runtime/reference/migration_guide/
• // TODO: does the following need to be wrapped in a try/catch too?
• // TODO: I think we want to be intentional about how we use try/catch here.
• // TODO: where would this log show up? Since this runs on Slack hosting in a lambda context
• // TODO: should we check that this is a ValidEventType at runtime?
• // TODO: if userland code has console.logs _outside_ of a function handler, at the top level scope of the module, _and_ the current execution is a local run and not a deployed-on-ROSI run,
• // TODO: latest version of std does not have a io/utils.ts
• // TODO: Update to import from deno-slack-hooks instead
• // TODO: type this to account for variable return options?