f12b4dc6b0
When deploying to Vercel, preview deployment URLs are dynamically generated. This breaks Live Preview within those deployments because there is no mechanism by which we can detect and set that URL within Payload. Although Vercel provides various environment variables at our disposal, they provide no concrete identifier for exactly _which_ URL is being currently previewed (you an access the same deployment from a number of different URLs). The fix is to support _relative_ live preview URLs, that way Payload can prepend the application's top-level domain dynamically at render-time in order to create a fully qualified URL. So when you visit a Vercel preview deployment, for example, that deployment's unique URL is used to load the iframe of the preview window, instead of the application's root/production domain. Note: this does not fix multi-tenancy single-domain setups, as those still require a static top-level domain for each tenant.
23 lines
499 B
TypeScript
23 lines
499 B
TypeScript
import config from '@payload-config'
|
|
import { type CollectionSlug, getPayload } from 'payload'
|
|
|
|
export const getDocs = async <T>(collection: CollectionSlug): Promise<T[]> => {
|
|
const payload = await getPayload({ config })
|
|
|
|
try {
|
|
const { docs } = await payload.find({
|
|
collection,
|
|
depth: 0,
|
|
limit: 100,
|
|
})
|
|
|
|
if (docs) {
|
|
return docs as T[]
|
|
}
|
|
} catch (err) {
|
|
throw new Error(`Error getting docs: ${err.message}`)
|
|
}
|
|
|
|
throw new Error('No docs found')
|
|
}
|