refactor(turbopack): Use ResolvedVc<T> for struct fields in next-api, final part
#47177
Annotations
10 errors and 1 warning
|
Run /bin/bash -c "./scripts/deploy-turbopack-docs.sh":
crates/next-api/src/route.rs#L33
cannot find type `ResolvedVc` in this scope
|
|
Run /bin/bash -c "./scripts/deploy-turbopack-docs.sh":
crates/next-api/src/route.rs#L34
cannot find type `ResolvedVc` in this scope
|
|
Run /bin/bash -c "./scripts/deploy-turbopack-docs.sh":
crates/next-api/src/route.rs#L37
cannot find type `ResolvedVc` in this scope
|
|
Run /bin/bash -c "./scripts/deploy-turbopack-docs.sh":
crates/next-api/src/route.rs#L42
cannot find type `ResolvedVc` in this scope
|
|
|
|
Run /bin/bash -c "./scripts/deploy-turbopack-docs.sh":
crates/next-api/src/server_actions.rs#L399
type mismatch resolving `<OptionActionMap as VcValueType>::Read == VcTransparentRead<OptionActionMap, Option<Vc<_>>, _>`
|
|
|
|
|
|
|
|
|
|
Run /bin/bash -c "./scripts/deploy-turbopack-docs.sh":
crates/next-api/src/versioned_content_map.rs#L158
unnecessary parentheses around `match` scrutinee expression
|
Loading