State of Disgo (v0.10.1)

[switchupcb]

State of Disgo (v0.10.1)

This State of Disgo will focus on the current features of Disgo in relation to the roadmap (to the v10 STABLE version).

Read about the previous State of Disgo (v0.10.0).

Developer Operations

I was gone for 3 months. To put into perspective how the decisions made in the previous state have helped, it took 3 hours to have Disgo updated and implementing all the new Discord features. Were those features supported (tested, etc)? Not yet. However, that's more of an issue with the unfinished state of Disgo than the workflow. In essence, the current developer operations are saving a LOT of time.

Static Code Analysis

The library remains linted and analyzed. I am considering adding a line linter to limit the maximum length of a line to half the width of a standard monitor (~100 character) for non-generated files.

Tests

At this time, Disgo's near-100% coverage of the Discord API test is still in development. The current coverage test allows the library to cover 14 endpoints, which are not dependent on other endpoints or used in examples. This constitutes 7% of the Discord REST API or 11% of the ideal coverage test. The main issue in finishing the coverage test is time. Ideally, there is a contributor who can pick this up (if it's even valued in the first place).

In theory, testing a certain percentage of the API would cover every endpoint because those endpoints implement the same patterns, which generated "implemented" endpoints cover.

Developer Ergonomics

Disgo places a high priority on simplicity for the end developer. As a reminder, one issue we found with other API Wrappers was the knowledge gap required to use them. The developer ends up having to learn how to use Go, the Discord API, AND the API Wrapper. In our case, the user only has to learn Go (and potentially the Discord API). This is because the API is based on the data and requests are represented as such.

Full Coverage

Disgo aims to implement every feature provided by the Discord API.

Dasgo

The Go API Types Library for the Discord API called Dasgo continues to become more stable. As a reminder, 3 months of content took 3 hours to implement. In contrast, updating when updates come out take a matter of minutes. Despite this, getting other members of the community to adopt it has not been possible. On one hand, the other wrappers are abstracted using functions; thus not designed to use the actual objects. On the other, there is no effort to migrate to Dasgo being made. Going forward, Dasgo adoption will likely scale with Disgo adoption.

Exclusive Features

See release notes. There are also more tools.

In other news, rate limits is solved.

Missing Features

See v10 release target.

Pre-Release

Disgo v0.10.1 is in a state that's close to stable. Development from v0.10.0 onwards was completed solely by me. However, I may not be as active (coding on Github) until late December or early January. As a result, another marketing push will be made throughout the month in an effort to gain contributors. Disgo is still in a state where contributors may be placed on the README (with a link to their websites). If you are interested in contributing to Disgo or the priority of incoming features, please read the roadmap.