Unverified Commit 7d09d1e6 authored by Tobias Koppers's avatar Tobias Koppers Committed by GitHub

Fix NextFontIssue IssueStage: CodeGen → Resolve (#92588)

### What?

Changes `NextFontIssue`'s `IssueStage` from `CodeGen` to `Resolve`.

### Why?

`NextFontIssue` is emitted during font resolution — when validating font
configuration options (`util.rs`) and when fetching/resolving Google
Font metadata (`google/mod.rs`, `google/font_fallback.rs`). None of
these occur during code generation; they all happen at the resolve stage
of the build pipeline.

Using `IssueStage::CodeGen` was incorrect and caused these font issues
to be grouped/sorted with code generation errors rather than resolution
errors. The local-font counterpart (`FontResolvingIssue` in
`next_font/local/mod.rs`) already correctly uses `IssueStage::Resolve`.

### How?

Single-line fix: change `IssueStage::CodeGen.cell()` to
`IssueStage::Resolve.cell()` in the `stage()` method of `impl Issue for
NextFontIssue`.

<!-- NEXT_JS_LLM_PR -->
Co-authored-by: 's avatarTobias Koppers <sokra@users.noreply.github.com>
Co-authored-by: 's avatarClaude <noreply@anthropic.com>
parent 5723c5a8
...@@ -14,7 +14,7 @@ pub(crate) struct NextFontIssue { ...@@ -14,7 +14,7 @@ pub(crate) struct NextFontIssue {
impl Issue for NextFontIssue { impl Issue for NextFontIssue {
#[turbo_tasks::function] #[turbo_tasks::function]
fn stage(&self) -> Vc<IssueStage> { fn stage(&self) -> Vc<IssueStage> {
IssueStage::CodeGen.cell() IssueStage::Resolve.cell()
} }
fn severity(&self) -> IssueSeverity { fn severity(&self) -> IssueSeverity {
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment