API coverage checklist

[not-so-smart]

Current state of API coverage

Groups

• Get active groups #4
  • Framework
  • Implementation
  • Tests
• Get former groups #5
  • Framework
  • Implementation
  • Tests
• Get single group by ID #6
  • Framework
  • Implementation
  • Tests
• Create group #7
  • Framework
  • Implementation
  • Tests
• Update group #8
  • Framework
  • Implementation
  • Tests
• Delete group #9
  • Framework
  • Implementation
  • Tests
• Join group #10
  • Framework
  • Implementation
  • Tests
• Rejoin former group #11
  • Framework
  • Implementation
  • Tests
• Transfer ownership #12
  • Framework
  • Implementation
  • Tests

Group Messages

• Get messages #13
  • Framework
  • Implementation
  • Tests
• Send message #14
  • Framework
  • Implementation
  • Tests
• Delete message #15
  • Framework
  • Implementation
  • Tests

Members

• Add members #16
  • Framework
  • Implementation
  • Tests
• Subtask: Fetch results of Add members #17
  • Framework
  • Implementation
  • Tests
• Remove member #18
  • Framework
  • Implementation
  • Tests
• Change nickname #19
  • Framework
  • Implementation
  • Tests

Chats

• Get chats #20
  • Framework
  • Implementation
  • Tests

Chat Messages

• Get messages #21
  • Framework
  • Implementation
  • Tests
• Send message #22
  • Framework
  • Implementation
  • Tests
• Delete message #23
  • Framework
  • Implementation
  • Tests

Users

• Get all blocks #24
  • Framework
  • Implementation
  • Tests
• Check for block from other user #25
  • Framework
  • Implementation
  • Tests
• Block user #26
  • Framework
  • Implementation
  • Tests
• Unblock user #27
  • Framework
  • Implementation
  • Tests

Likes

• Like message #28
  • Framework
  • Implementation
  • Tests
• Unlike message #29
  • Framework
  • Implementation
  • Tests
• Get leaderboard #30
  • Framework
  • Implementation
  • Tests
• Get given likes #31
  • Framework
  • Implementation
  • Tests
• Get received likes #32
  • Framework
  • Implementation
  • Tests

Calendar

• Get events #33
  • Framework
  • Implementation
  • Tests
• Create event #34
  • Framework
  • Implementation
  • Tests
• Update event #35
  • Framework
  • Implementation
  • Tests
• Delete event #36
  • Framework
  • Implementation
  • Tests
• Add RSVP #37
  • Framework
  • Implementation
  • Tests
• Undo RSVP #38
  • Framework
  • Implementation
  • Tests

Account

• Get details #39
  • Framework
  • Implementation
  • Tests
• Update details #40
  • Framework
  • Implementation
  • Tests
• Enable SMS #41
  • Framework
  • Implementation
  • Tests
• Disable SMS #42
  • Framework
  • Implementation
  • Tests

Polls

• Create poll #43
  • Framework
  • Implementation
  • Tests
• Get all polls #44
  • Framework
  • Implementation
  • Tests
• Get poll by ID #45
  • Framework
  • Implementation
  • Tests
• Vote #46
  • Framework
  • Implementation
  • Tests
• End poll #47
  • Framework
  • Implementation
  • Tests

Attachments

• Upload image #48
  • Framework
  • Implementation
  • Tests
• Upload video #49
  • Framework
  • Implementation
  • Tests
• Upload File #50
  • Framework
  • Implementation
  • Tests

Push

• Implement push events

Miscellaneous and v4 stuff

• Pending memberships
• Relationships

Bots (ignored for now)

[AlureonTheVirus]

not that I can speak for the project but I'd like to add that groupme has also added subgroups as what it calls "topics".

I assume that we will want to have websocket support at some point built in. A more Event-Driven approach would make bot development with this library a lot simpler and more straightforward/intuitive. (Let me know if I'm wrong and that's already implemented.)

It also seems that this project lacks a lot of in depth documentation and examples that other API wrappers typically have. (Not a diss, just an observation and possibly another goal to work towards.)

[not-so-smart]

not that I can speak for the project but I'd like to add that groupme has also added subgroups as what it calls "topics".

Thank you! Yes, we do want to add support for topics, currently there is no framework for it but feel free to open a PR if you'd like to get that started :)

I assume that we will want to have websocket support at some point built in. A more Event-Driven approach would make bot development with this library a lot simpler and more straightforward/intuitive. (Let me know if I'm wrong and that's already implemented.)

Good news! The PR for websockets (#104) is currently open and will be merged soon! :D

It also seems that this project lacks a lot of in depth documentation and examples that other API wrappers typically have. (Not a diss, just an observation and possibly another goal to work towards.)

Yes, as you can see from this checklist, a lot of the framework (files, classes and method stubs to shape the relevant data structures) and even most of the implementation (filling in those method stubs with code that interacts with the API) is currently missing. API coverage is a slightly higher priority than documentation at this stage, but we do have docs at https://groupme.js.org/ which are automatically generated on each release and built from TS type information (for classes and their properties) along with any JSdoc comments present in the code (for descriptions of these objects and example usage). If you want to add to this documentation, just open a PR adding comments following the JSdoc standard (https://jsdoc.app/) and they'll be added to the generated docs in the next build.