SeatReservation | 图书馆座位自动预约

The new seatReservation('D3') creates a function which will, when called, return the secret passed to it. You could for example do: console.log(seat());. You call the function, thus retrieving the data from the closure.

For the seat reservation, I think it would make sense to use repeated field. Just like real world scenario, the request is like "I want seat A, B, C for movie X", which is more like repeated manner than streaming. thus, the payload is very small. Also, this way should use less server resource since it is a batch process.

I think you understand what's happening and why it breaks your code, but are still looking for an explanation on when you actually need to use optionsValue, and when not.

Let's say your meals can be sold out and you want to check with the server for updates in availableMeals:

Something looks wonky to me in your relationship and query definitions. It looks to me like Seats hasMany SeatReservations (one for each year) not hasOne.

Also, your code probably doesn't work because a particular seat may have no reservations in which case you'll never get to thisyear() to check the count.

I think you need to change how you call your relation. See: Laravel. Use scope() in models with relation

Something like this might work: