Skip to content

Commit

Permalink
chore: fixed license mention on README
Browse files Browse the repository at this point in the history
  • Loading branch information
@lucasconstantino
lucasconstantino committed Jan 9, 2023
1 parent e81ad22 commit b3093b4
Showing 1 changed file with 0 additions and 8 deletions.
8 changes: 0 additions & 8 deletions README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -213,9 +213,6 @@ Checkout the [./examples/redis](./examples/redis/) project for a complete, yet s

## Future vision

<details>
<summary>Read more</summary>

I expect that eventually Next.js will provide an API for tagging pages. As of data-source for the cache-tags registry, it could the same storage where it stores rendered pages (S3 bucket? Probably...). Alternatively, it could integrate with [Edge Config](https://vercel.com/docs/concepts/edge-network/edge-config) for ultimate availability and performance on writting/reading from the cache-tags registry.

I can imagine that this could become as simple as adding an extra property to the returned object from `getStaticProps`. Something on these lines:
Expand All @@ -236,8 +233,3 @@ export const getStaticProps = async () => {
}
```

</details>

## License

ISC

1 comment on commit b3093b4

@vercel
Copy link

@vercel vercel bot commented on b3093b4 Jan 9, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Successfully deployed to the following URLs:

next-cache-tags-redis-example – ./

next-cache-tags-redis-example.vercel.app
next-cache-tags-redis-example-git-main-lucasconstantino.vercel.app
next-cache-tags-redis-example-lucasconstantino.vercel.app

Please sign in to comment.