Feature/rpc#170
Conversation
# Conflicts: # discord/activity.go # go.mod # go.sum
|
is there still interest in continuing RPC development? if so, I could look at picking up some work for this. |
|
If I recall correctly the status is that most stuff has been implemented, but I wasn't happy with the API design. If you have interest in picking this up I have no objections |
|
"wasn't happy with the API design" Can you elaborate? I can see in the example that you need to manually authorize etc. Is that what you're referring to? |
|
I am referring to how the send requires a callback to be passed to handle the answer |
|
Ah, gotcha. I've seen another library (Rich Presence only) handle it by returning the value, so it should definitely be possible to get working for this as well. I'll have a look into that. |
|
that would be the ideal solution, but ideally this would be made 100% type safe using generics which is the challenge |
|
if you want to chat more about these changes, feel free to join our discord |
# Conflicts: # discord/application.go # go.mod # go.sum
|
what happened to this ;-; |
|
no motivation/usecase/other things to do |
lost interest in figuring out Discord's broken docs on all types of messages it could send |
|
honestly, makes sense. |
No description provided.