694c76d51a
The `fields-relationship` test suite is disorganized to the point of being unusable. This makes it very difficult to digest at a high level and add new tests. This PR cleans it up in the following ways: - Moves collection configs to their own standalone files - Moves the seed function to its own file - Consolidates collection slugs in their own file - Uses generated types instead of defining them statically - Wraps the `filterOptions` e2e tests within a describe block Related, there are three distinct test suites where we manage relationships: `relationships`, `fields-relationship`, and `fields > relationships`. In the future we ought to consolidate at least two of these. IMO the `fields > relationship` suite should remain in place for general _component level_ UI tests for the field itself, whereas the other suite could run the integration tests and test the more complex UI patterns that exist outside of the field component.
9 lines
164 B
TypeScript
9 lines
164 B
TypeScript
import type { CollectionConfig } from 'payload'
|
|
|
|
export const baseRelationshipFields: CollectionConfig['fields'] = [
|
|
{
|
|
name: 'name',
|
|
type: 'text',
|
|
},
|
|
]
|