Trevor Hartman
Trevor Hartman
- Should it break on the first error? - Or collect all errors and surface their messages?
`name` and `key` are deprecated: https://developer.atlassian.com/cloud/jira/platform/rest/v3/#api-rest-api-3-issue-issueIdOrKey-assignee-put - assign issue - update issue to change assignee - create issue with assignee
- Mention it in the output of help too - apropos like functionality? Once we have decent coverage maybe we can leverage it for more helpful hints when a user...
https://kroki.io/ e.g. https://kroki.io/graphviz/svg/eNp9kM0KgzAQhO8-xZIHaKlX6Ulp6S-FPoDEuGhqbML6cyl594JVGyv1OMPMt8ukMiNucojg5QFUTfKRQjVVjRSbzgZQPEEFW2An0oVkQWfO0mLTx53CHalF6hsAO6kwQV4PesbIRPylOJxIiwJp_YMDOPKWD8ouQP0F6AWp5DJ1qOyqU1w9Kte6NcZgjZPrLMxJl8imH9g_8_jzecLzYSzvteLPLBgR1rNvJ7Rwmw==
`xargs` uses `command-execution-info`. Currently it's preventing use of sub-exprs in `xargs`. Remove the restriction and test to make sure it doesn't break anything.
Default it to `[]` automatically so the user doesn't have to. - Add tests in https://github.com/yetibot/yetibot.core/blob/master/test/yetibot/core/test/db/util.clj - Create the default value here https://github.com/yetibot/yetibot.core/blob/34765cd6d46df09c4ebb9701556291350f5efab4/src/yetibot/core/db/util.clj#L89-L106
https://api.slack.com/methods/emoji.list Could imagine being able to use it in combination with `react`, like: ``` slack emoji | random | react ```
Currently we use `rate-gate` which just drops calls if they happen too fast: [see code](https://github.com/yetibot/yetibot.core/blob/e132eaad635046d5b7fbe7605909436720d565cb/src/yetibot/core/adapters/irc.clj#L39-L41). Instead we should use something that just limits the rate at which messages are sent...
`watch`
run command on an interval and watch its output for a match. `!watch 20 Currently.building..false jen status foo` `watch # run command every seconds until its output matches `