discord-hs alternatives and similar packages
Based on the "Networking" category.
Alternatively, view discord-hs alternatives based on common mentions on social networks and blogs.
-
-
-
-
-
-
-
-
-
call-haskell-from-anything
Call Haskell functions from any programming language via serialization and dynamic libraries -
-
PortFusion
Haskell-powered cross-platform transport-layer distributed reverse / forward proxy & tunneling solution – currently available for all TCP protocols (RDP, VNC, HTTP(S), SSH, ...). -
-
-
-
-
-
-
-
-
-
-
-
-
ngx-export
A comprehensive web framework aimed at building custom Haskell handlers for the Nginx Web Server -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
InfluxDB – Built for High-Performance Time Series Workloads
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of discord-hs or a related project?
README
Discord.hs
A Haskell wrapper for the Discord API
Using in a project
The preferred (and only supported) method of using discord.hs is through stack. Open your stack.yaml
and find the extra-deps section. Add the following:
extra-deps:
- discord-hs-0.2.1
Then open your project.cabal file and add discord-hs to your build-depends.
Alternatively, you can add discord-hs to your project.cabal file, and run
stack solver --update-config. This will let stack catch other missing dependencies
in your project and is most likely the better option.
PingPong
{-# LANGUAGE OverloadedStrings, RecordWildCards #-}
import Data.Text
import Pipes
import Network.Discord
reply :: Message -> Text -> Effect DiscordM ()
reply Message{messageChannel=chan} cont = fetch' $ CreateMessage chan cont Nothing
main :: IO ()
main = runBot (Bot "TOKEN") $ do
with ReadyEvent $ \(Init v u _ _ _) ->
liftIO . putStrLn $ "Connected to gateway v" ++ show v ++ " as user " ++ show u
with MessageCreateEvent $ \msg@Message{..} -> do
when ("Ping" `isPrefixOf` messageContent && (not . userIsBot $ messageAuthor)) $
reply msg "Pong!"
Known issues:
- Init isn't parsing correctly
- Client doesn't close correctly
- Missing voice support