Repository navigation
Conversation
A mistyped task setting such as `cache: { outputs: [...] }` failed with
"data did not match any variant of untagged enum UserTaskDefinition".
Deserialize `UserTaskDefinition` and `UserCacheConfig` by value type so
the error of the form the user wrote is shown instead.
Refs voidzero-dev/vite-plus#2635
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
Refs voidzero-dev/vite-plus#2635
Motivation
A mistyped setting in a task, such as
cache: { outputs: ["dist/**"] }(the field isoutput), fails with an error that names neither the key nor what is accepted:UserTaskDefinitionandUserCacheConfigwere#[serde(untagged)], which discards each variant's own error. They now pick the variant from the value's type, so the real error comes through:Valid configs parse as before and
run-config.tsis unchanged. The error still doesn't name the task; that needs path tracking in the config loaders.The main report in the issue (a cache hit that doesn't restore files) is already fixed by #461.
AI-assisted with Claude Opus 5.5.