fix: build prompt enum dropdowns from codegen instead of runtime introspection - #465
Merged
Merged
Conversation
The four __type introspection queries fired together on form load; when the backend was slow the browser aborted them and staleTime: Infinity cached the failure, leaving Task Type / Domain / Target Languages / Target Model Types empty until a reload. Enum values are fixed at build time, so read them from the generated enums instead.
Same abort-and-cache failure as the metadata form; also drops a debug effect that logged the whole enum payload to the console.
Contributor
Author
|
@Abhishekfm please look at this fix once. |
This was referenced Sep 16, 2026
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
1 participant
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.
Closes #463.
What: Task Type, Domain, Target Languages, Target Model Types and Prompt Format were populated by
__typeintrospection queries fired on form load. Four went out together; when the backend was slow the browser aborted them, andstaleTime: Infinitycached the failure, so the fields stayed empty until a reload.Evidence: dev nginx logged
POST /api/graphql499 in bursts of four;test_prv_006bfails with the correct field focused and 'No results found'.Fix: read the values from the generated enums (
PromptTaskType,PromptDomain,TargetLanguage,TargetModelType,PromptFormat) via a one-linelib/enumValues.ts. Label formatting is unchanged at every call site, so the visible options are identical. No__type(name:query remains in the app.Checks:
tsc --noEmitreports the same 10 pre-existing errors as clean dev, none in the changed files.