Alexander Cobleigh

thanks for making an issue on this @khubo! just gonna brainstorm a bit --- so we have the client object typically, e.g. ``` const Client = require("cabal-client") const client =...

ah nice, i remember @noffle and i had some discussions about the format to send. i forget what we came up with though, i'll look through my logs :~

@khubo @noffle here are the notes: https://gist.github.com/cblgh/787e78a3479a4b0801bee2768933ffda it was apparently karissa and noffle brainstorming! and here's the hackmd the discussion was based on https://hackmd.io/BeZ49Q2ARZavH1v2JbbJKw

btw @khubo the `api.md` file is autogenerated using the comments from the source code! if you look at the code description of [`publishMessage`](https://github.com/cabal-club/cabal-client/blob/b165da7e59e743f90450dbc63a20cf73e7f12654/src/cabal-details.js#L73-L88) you can see a good example :3...

yeah +1 on gettin it workin & iterating on it :3 i can help you test throughout the week ^_^

fwiw it might be worth treating images separately, or including a metadata field as part of the chat/files message schema. reason being that we can then always display file messages...

@telamon i don't know why it doesn't work, but it's from https://github.com/cabal-club/cabal-client/pull/11 the comment contains everything (except i guess the context of the particular code snippet) that noffle originally posted

thanks for the issue, tim! I'll have to dive back into this again at some point it seems :) the commit linked was basically trying to figure out an issue...

@timgoeller where are you seeing the issues btw, in one of your cabal-bot repos?

lmk how i can help @timgoeller! it'd be a great way for me to ease into dev again tbh :~