Update core to use mattermostautodriver instead of mattermostdriver #337
Conversation
|
Can you enable issues on that repo? 😄 Seems like the docs (https://embl-bio-it.github.io/python-mattermost-autodriver/) are broken: |
|
Issues enabled now. Docs are indeed still broken. I still didn't get around generating them as some of the auto-generated docstrings are quite messy. I'll spend some time today digging into why integration tests are failing. |
|
Seems like integration test failures will also fail on |
unode
force-pushed
the
autodriver
branch
3 times, most recently
from
65c2073 to
51053d0
Compare
|
@attzonko this is now ready. There were some issues with the new driver that should have now all been resolved. |
also add DeprecationWarning
|
Code Climate has analyzed commit b322c12 and detected 0 issues on this pull request. View more on Code Climate. |
…ttzonko#337) * create_ephemeral_post -> create_post_ephemeral * create_reaction -> save_reaction * create_direct_message_channel -> create_direct_channel * get_channels_for_user -> get_channels_for_team_for_user * get_thread -> get_post_thread * get_reactions_of_post -> get_reactions * webhooks.call_webhook -> call_webhook * mattermostdriver -> mattermostautodriver
As discussed at Vaelor/python-mattermost-driver#100 the latest release of
mattermostdriveris missing several API endpoints. The fork python-mattermost-autodriver uses an approach that transforms Mattermost's OpenAPI documentation to Python code, ensuring all endpoints are readily available.The current PR updates the core of mmpy_bot to use the new API driver. The core functionality is the same but as endpoints were automatically generated, some functions have different names. Unless I missed some, this PR should address all of them.