evpav

I find this strange too. Take the guide example: ```php $customer = Customer::findOne(123); $order = new Order(); $order->subtotal = 100; // ... $order->customer_id = $customer->id; $order->save(); // or: $order->link('customer', $customer);...

@cebe, that's just two examples from the guide combined here for brevity, they are not used together, but supposed to be alternatives.

That I know, the question is why `link` combines setting the FK value and saving the related record, but doesn't provide a way to either validate the record after setting...

With M:N relations `link` goes through a different code path, and usually doesn't require validation of the junction table records. With simple 1:N relations an extra `link` argument to pass...

If there is a typo or a misspelling in a type declaration ValidateVar does not perform any actual validation and just silently returns the original value.

Well, not only from fools. For example, `int`/`integer`, `bool`/`boolean` are acceptable in phpdocs, but only short forms will be "validated" here. It is not mentioned in the docs and can...

> Actually I cant see any benefits here. Strict type validation becomes to something else. That is a valid way to describe union types without creating weird class hierarchies or...

Supporting multiple types doesn't mean omitting strict type validation. I know that in the current state this PR doesn't provide very useful error messages, but it can be improved if...