Skip to content

fix: allow locally-running functions to access files.slack.com #9

fix: allow locally-running functions to access files.slack.com

fix: allow locally-running functions to access files.slack.com #9

GitHub Actions / Health Score completed Jul 30, 2024 in 0s

-1000

-1000 health score points

Details

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: latest version of std does not have a io/utils.ts
  • // TODO: Update to import from deno-slack-hooks instead
  • // TODO: should we check that this is a ValidEventType at runtime?
  • // TODO: type this to account for variable return options?
  • // 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: 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

Annotations

Check warning on line 10 in src/run-function.ts

See this annotation in the file changed.

@github-actions github-actions / Health Score

src/run-function.ts#L10

Problematic comment ("TODO") identified

Check warning on line 12 in src/run-function.ts

See this annotation in the file changed.

@github-actions github-actions / Health Score

src/run-function.ts#L12

Problematic comment ("TODO") identified

Check warning on line 1 in src/deps.ts

See this annotation in the file changed.

@github-actions github-actions / Health Score

src/deps.ts#L1

Problematic comment ("TODO") identified

Check warning on line 4 in src/deps.ts

See this annotation in the file changed.

@github-actions github-actions / Health Score

src/deps.ts#L4

Problematic comment ("TODO") identified

Check warning on line 45 in src/dispatch-payload.ts

See this annotation in the file changed.

@github-actions github-actions / Health Score

src/dispatch-payload.ts#L45

Problematic comment ("TODO") identified

Check warning on line 83 in src/types.ts

See this annotation in the file changed.

@github-actions github-actions / Health Score

src/types.ts#L83

Problematic comment ("TODO") identified

Check warning on line 17 in src/load-function-module.ts

See this annotation in the file changed.

@github-actions github-actions / Health Score

src/load-function-module.ts#L17

Problematic comment ("TODO") identified

Check warning on line 81 in src/mod.ts

See this annotation in the file changed.

@github-actions github-actions / Health Score

src/mod.ts#L81

Problematic comment ("TODO") identified

Check warning on line 84 in src/mod.ts

See this annotation in the file changed.

@github-actions github-actions / Health Score

src/mod.ts#L84

Problematic comment ("TODO") identified

Check warning on line 98 in src/mod.ts

See this annotation in the file changed.

@github-actions github-actions / Health Score

src/mod.ts#L98

Problematic comment ("TODO") identified