Generate possibleTypes.json without running the backend - #234
Merged
Conversation
isakstenstrom
marked this pull request as draft
April 22, 2026 06:17
This was referenced Apr 22, 2026
Merged
isakstenstrom
force-pushed
the
generate-possible-types
branch
from
April 29, 2026 06:29
fa08cdc to
f9409ae
Compare
isakstenstrom
marked this pull request as ready for review
April 29, 2026 14:19
meroton-benjamin
approved these changes
May 4, 2026
This makes it easier to run it in CI.
isakstenstrom
force-pushed
the
generate-possible-types
branch
from
May 4, 2026 11:55
f9409ae to
93e27e6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
NOTE: This is a stacked PR. Please merge #226, #227, #228, #229, #230, #231, #232, #233 first.
Instead of extraction all possible API types from the API, we instead use the Graphql schema files. This makes it possible to do it without having the backend running, allowing us to run it in the normal frontend generation step, and thus in CI.
Previously it was almost always outdated, but now it will be kept in sync.