9c8f3202e4
## What Before this PR, an internal link in the Lexical editor could reference a document from a different tenant than the active one. Reproduction: 1. `pnpm dev plugin-multi-tenant` 2. Log in with `dev@payloadcms.com` and password `test` 3. Go to `http://localhost:3000/admin/collections/food-items` and switch between the `Blue Dog` and `Steel Cat` tenants to see which food items each tenant has. 4. Go to http://localhost:3000/admin/collections/food-items/create, and in the new richtext field enter an internal link 5. In the relationship select menu, you will see the 6 food items at once (3 of each of those tenants). In the relationship select menu, you would previously see all 6 food items at once (3 from each of those tenants). Now, you'll only see the 3 from the active tenant. The new test verifies that this is fixed. ## How `baseListFilter` is used, but now it's called `baseFilter` for obvious reasons: it doesn't just filter the List View. Having two different properties where the same function was supposed to be placed wasn't feasible. `baseListFilter` is still supported for backwards compatibility. It's used as a fallback if `baseFilter` isn't defined, and it's documented as deprecated. `baseFilter` is injected into `filterOptions` of the internal link field in the Lexical Editor.
15 lines
262 B
TypeScript
15 lines
262 B
TypeScript
export const credentials = {
|
|
admin: {
|
|
email: 'dev@payloadcms.com',
|
|
password: 'test',
|
|
},
|
|
blueDog: {
|
|
email: 'jane@blue-dog.com',
|
|
password: 'test',
|
|
},
|
|
owner: {
|
|
email: 'owner@anchorAndBlueDog.com',
|
|
password: 'test',
|
|
},
|
|
} as const
|