Christopher Jr Riley

Results 13 issues of Christopher Jr Riley

### Summary _No response_ ### Pain points The current implementation of ATProtoKit lacks a centralized logging mechanism, leading to several challenges, namely that debugging is much more difficult to deal...

good first issue
enhancement

## Description Describe in detail what this Pull Request does and why it’s needed. Include anything the reviewers need to be aware of. This Pull Request re-organizes all of the...

documentation
enhancement

### Summary Create methods that deal with creating, editing, and deleting records. ### Pain points While it's possible for API users to create methods for creating, editing, and deleting record...

documentation
new feature
good first issue

### Summary _No response_ ### Pain points Currently, the structure of the models work out like this: - The file name of the applicable model(s) contains the domain name, the...

documentation
enhancement

### Summary _No response_ ### Pain points `ATImageProcessable` is a helper protocol framework that tries to get images down to below the maximum size that the AT Protocol requires. Since...

new feature
good first issue

### Summary At this time, builds for platforms other than macOS are failing. This will need to be resolved in order to achieve the goal of having ATProtoKit be used...

bug
new feature

### Summary Create a solution where the `@DateFormatting` property wrapper is able to handle all of the requirements without the need to create custom implementations. ### Pain points At this...

good first issue
enhancement

### Summary Create a solution for not only creating lexicons, but also converting them into Swift models and methods. ### Pain points At this time, all lexicon models and methods...

new feature
draft

### Summary An article needs to be written on how to get a record with one line, as well as how to handle the `ATUnion` type. ### Description For version...

documentation

### Summary The DocC has several inconsistencies and navigational issues ### Description Several pages in the DocC are either outdated, inconsistent, difficult to read and understand, and/or out of place....

documentation
good first issue