Sometimes optional fields

[chris-hud]

Is there an accepted practice to deal with sometimes optional fields?
Optional fields are defined here

However, I often will have fields that are required on the model, but then create a method to update only a piece of the model, often only sending the relevant data over the wire, not the whole model. Essentially I need the fields to be optional for some requests, but not for others.

order model
seller_name, required
buyer_name, required
seller_address, required
buyer_address, required
delivered, nullable

createOrder(Request $request) {
    Validator::make($request->all(), [
        'seller_name' => 'required|max:255',
        'buyer_name' => 'required|max:255',
        'seller_address' => 'required|max:255',
        'buyer_address' => 'required|max:255',
    ])->validate();
...
}

updateOrderDeliveryStatus(Request $request) {
  Validator::make($request->all(), [
        'order_id' => 'required|Integer',
        'delivered' => 'required|Boolean',
    ])->validate();
...
}

updateSellerName(Request $request) {
  Validator::make($request->all(), [
        'order_id' => 'required|Integer',
        'seller_name' => 'required|max:255',
    ])->validate();
...
}

[TheFerrettDeveloper]

Bumping because I too would like to know.

[hettiger]

I'm also interested in this. Bump

[backstageel]

I am also looking for this