othercorey

This is using the default behavior of DateTimeImmutalbe;:createFromFormat(). I don't think we'll be able to detect a time component wasn't included in the format.

The current behavior is to use the type hint if no annotation exists and all parameters are listed in the block. These are often just duplicates of the data in...

I request adding "Move under Cake/ namespace".

I'm not going to make a big issue out of this, but my point-of-view is that we shouldn't be pushing things into the top-level namespace just because. I'm not a...

Should we trim and merge or close this?

> I think this could be accompanied by a second query like `SELECT SCOPE_IDENTITY();` to retrieve the `ID`. What are the restrictions when using this query? Is is just the...

Looks to me. The new coercion functions seem to have a reasonable equivalent. The only concern I have is float values are coerced to an integer.

Maybe we can add a parameter on strictness for int coercion so the controller behavior can be kept.

> We could put a configure flag in place? We could try having behavior changes like this being behind 'feature flags' that let you opt-in to the old behavior. I've...

I was looking at the float to int cast instead of the string conversion that the controller param would use. Guess there is some reason int min isn't allowed?