![]() ![]() ![]() I did close issues that were missing information or were filed against some ancient version of Rocket.Chat.I’m thankful in advance already What I did and what I didn’t do If you see those, point them out to me, correct them and put things right. I can only interpolate from the things I see on Github / other Rocket.Chat means of public communication.Īlso I most certainly made mistakes or have thoughts that might be wrong. I will try to restrain myself, but you know how it is, when you are involved with something…Īlso, my critique might, in some places, not be fully justified because I don’t see the inner workings of the Rocket.Chat Company. If you can’t handle that, please move on. That being said: I am going to criticize things and I will most probably be using strong language. Otherwise I wouldn’t have invested such a huge amount of my spare time (this post alone took me 3h). Quite obviously, I have an interest in Rocket.Chat flourishing. This post tries to capture this experience and derive actionable information from it. I won’t say that I have looked at every single issue but I combed through every page to find issues that are not relevant anymore, don’t provide enough information or in some other way justify to close the respective issue. At the time of writing this, I have closed 106 issues with the help of this bot and skimmed the >90 pages of open issues in the process. Together with with Theo Renck and we got a prototype of a Github bot off the ground that I used to delve into the depths of the Rocket.Chat Github repository, more precisely their open bugs. In lights of the breathtakingly high number of open issues I asked, whether it would make sense to give github moderation privileges to assorted community members. JetBrains supports this project by providing us with licenses for their fantastic products.First off: this is a follow up to Possibility of Github moderation for community members - #36 by sing.li. Reporting bugs and asking for features is also contributing ) Feel free to help us grow by registering issues. Please, try to implement tests for all your code and use a PEP8 compliant code style. (It may take a while to merge your code but if it's good it will be merged). You can contribute by doing Pull Requests. To start test server do docker-compose up and to take test server down docker-compose down.Tests run on a Rocket.Chat Docker container so install Docker and docker-compose. If you are interested in a specific call just open an issue or open a pull request. Most of the API methods are already implemented. For a detailed parameters list check the Rocket chat API API coverage Only required parameters are explicit on the RocketChat class but you can still use all other parameters. ![]() json ()) Using a token for authentication instead of user and password from pprint import pprint from rocketchat_API.rocketchat import RocketChat rocket = RocketChat ( user_id = 'WPXGmQ64S3BXdCRb6', auth_token = 'jvNyOYw2f0YKwtiFS06Fk21HBRBBuV7zI43HmkNzI_s', server_url = '' ) pprint ( rocket. channels_history ( 'GENERAL', count = 5 ). chat_post_message ( 'good news everyone!', channel = 'GENERAL', alias = 'Farnsworth' ). Session () as session : rocket = RocketChat ( 'user', 'pass', server_url = '', session = session ) pprint ( rocket. from requests import sessions from pprint import pprint from rocketchat_API.rocketchat import RocketChat with sessions. This will save significant time by avoiding re-negotiation of TLS (SSL) with the chat server on each call. If you are going to make a couple of request, you can user connection pooling provided by requests. Note: every method returns a requests Response object. Usage from pprint import pprint from rocketchat_API.rocketchat import RocketChat proxy_dict = rocket = RocketChat ( 'user', 'pass', server_url = '', proxies = proxy_dict ) pprint ( rocket. Clone our repository and python3 setup.py install
0 Comments
Leave a Reply. |