Skip to content

Searching for conflicts requires a field 'slug' in the entity #7

@cammanderson

Description

@cammanderson

I know it is implied (e.g. get/set slug), but you may want to implement a naming convention around slugs, such as meta_slug or similar. Is it possible to refactor somehow so that entities can declare what the field is to search on? Thinking like how the security package configures the username field (e.g. in security with the entity section).

Currently the Listener uses the repository to search for conflicts based on the slug field.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions