Unverified Commit eee419ea authored by Joseph's avatar Joseph Committed by GitHub

docs: revalidateTag requires second argument (#85284)

Closes: https://github.com/vercel/next.js/issues/85281
parent f3656691
...@@ -26,7 +26,7 @@ The revalidation behavior depends on whether you provide the second argument: ...@@ -26,7 +26,7 @@ The revalidation behavior depends on whether you provide the second argument:
## Parameters ## Parameters
```ts ```ts
revalidateTag(tag: string, profile?: string | { expire?: number }): void; revalidateTag(tag: string, profile: string | { expire?: number }): void;
``` ```
- `tag`: A string representing the cache tag associated with the data you want to revalidate. Must not exceed 256 characters. This value is case-sensitive. - `tag`: A string representing the cache tag associated with the data you want to revalidate. Must not exceed 256 characters. This value is case-sensitive.
...@@ -52,6 +52,8 @@ async function getData() { ...@@ -52,6 +52,8 @@ async function getData() {
} }
``` ```
> **Good to know**: The single-argument form `revalidateTag(tag)` is deprecated. It currently works if TypeScript errors are suppressed, but this behavior may be removed in a future version. Update to the two-argument signature.
## Returns ## Returns
`revalidateTag` does not return a value. `revalidateTag` does not return a value.
......
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