Skip to content

Recommendation for working around required fields in drafts? #21

@ChrisHardie

Description

@ChrisHardie

We're looking at using drafts to allow someone to create a model without filling in all of the usually required fields when the needed information is not yet available, but when creating a draft is still helpful.

Do you have any recommendations or experience with how to do that? I think it requires more than just checking the status of the model as draft/published in a ->required() callback, as the transition from draft to published would have to be handled too.

Thanks for any guidance you can offer!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions