Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Send invite to conversation #84

Open
grigori-gru opened this issue Jan 30, 2018 · 5 comments
Open

Send invite to conversation #84

grigori-gru opened this issue Jan 30, 2018 · 5 comments

Comments

@grigori-gru
Copy link
Contributor

Hello! Nice work) We use your project in matrix-skype-puppet. Is there any way to add someone from contacts to the chat group/conversation using your api? Maybe it's somehow possible by sending them 'share link' but I can't find how to get it?

@demurgos
Copy link
Member

demurgos commented Jan 30, 2018

Hi, thanks for using the library and reporting issues. I'm now watching your project: it has some interesting issues (some of them were also fixed on master, you can install it with skype-http@next, but it also has breaking changes due to the new contact API).

Regarding the addition of contacts, it is currently not possible but I'd like to have it. If you want to help, I'd be happy to help you and eventually give you write access (it may help with your library).
The first step would be to find how Skype does it. I usually do 3 things: check the HTTP requests of the web client when I perform the action, check SkPy (a Python library for Skype) or look into their source code.

I'm currently in the process of updating the conversation API so it may be the occasion to add it. I'll try to merge my changes quickly.

I am trying to move this library to be a thinner wrapper around Skype: it would focus on abstracting the HTTP calls and guaranteeing the properties on the return values with runtime checks. It currently manually remaps some of the objects but it gets harder to maintain. Also I used typedoc to generate documentation but this no longer works well, so I need to better document it and find a workaround.

@grigori-gru
Copy link
Contributor Author

Thanks for feedback! I'll check it out and let you know if find out how Skype does it.

@demurgos
Copy link
Member

demurgos commented Feb 2, 2018

I'm re-opening until it is supported.

@demurgos demurgos reopened this Feb 2, 2018
@grigori-gru
Copy link
Contributor Author

@demurgos
As I see you're going to remove checking EventMessage.resourceType in the next version?

@demurgos
Copy link
Member

See my reply in the PR thread

You'll still need to check event.resourceType: there will be more events (endpoint and user presence) discriminated by this property. Also for messages event.resource.type becomes event.resource.messageType to match the real Skype API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants