Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

misc: Initial addition of IGDB typehints #1265

Merged
merged 1 commit into from
Oct 29, 2024

Conversation

adamantike
Copy link
Collaborator

The short-term goal is to completely typehint the IGDB API responses. This first change adds the base structures and enums RomM currently uses.

The ExpandableField type will allow us to model the expansion mechanism the IGDB API provides, where a field can include either an ID, or the full nested structure.

Copy link

github-actions bot commented Oct 27, 2024

Test Results

88 tests  ±0   88 ✅ ±0   29s ⏱️ +3s
 1 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit 4bb5cb5. ± Comparison against base commit 373757e.

♻️ This comment has been updated with latest results.

The short-term goal is to completely typehint the IGDB API responses. This
first change adds the base structures and enums RomM currently uses.

The `ExpandableField` type will allow us to model the expansion
mechanism the IGDB API provides, where a field can include either an ID,
or the full nested structure.
@zurdi15
Copy link
Member

zurdi15 commented Oct 27, 2024

Great idea! This will help to make the API interaction much robust

@adamantike adamantike merged commit 009a436 into master Oct 29, 2024
8 checks passed
@adamantike adamantike deleted the misc/initial-igdb-typehints branch October 29, 2024 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants