![]() ![]() A few examples of events similar to those emitted internally by Slacker: Any additional arguments passed toĮmit! are passed as arguments to functions registered as handlers for the The first argument is a required topic, which is suggested to take the type ofĪ keyword, but no restrictions are enforced. Disagreements are welcome and should beĪn event can be emitted using slacker.client/emit!. For now this has not felt awkwardĪnd has not limited expressiveness. Guarantees it will not change in the future. Sensible design decision underpinning this decisive choice, and there are no Indeed desirable for the bots currently built on top of Slacker. Why? It's a really simple implementation and nothing more seems necessary or It seems prudent to be up-front aboutĮmitted events are fully asynchronous and anonymous, emitted in a different Listening, you might reason that they did. Emitting eventsĮmitting an event in Slacker is like shouting from your balcony in the the dark. Surely documented and kept up to date in the appropriate part of this README. Slackerĭoes not sit idly by and generates a number of events of its own. ![]() The topics include those from Slack,īut manhandled into a more Clojurian format of :keywords-with-dashes. Slack network, Slacker will emit topical events to any interested listenerįunctions. The library revolves around emitting and handling events. Intermediate complexity bots, but beyond clinging to this rationale as anĮxcuse for maintaining a rather meager feature set, it does not limit yourĪbility to write a regular Slack client or interacting with Slack in other ways. It caters primarily to the creation of simple to Slacker is an enthusiastically asynchronous library for interacting with An enthusiastically asynchronous Slack bot library. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |