Mark Scherer

Turns out, the wrapping method already expects mixed. /** * Get the value of the "name" from HTTP GET arguments. * * @return mixed */ public function value(): mixed {...

Are we OK to merge here?

@ndm2 So you think we shouldn't merge this?

Currently, phinx serves as a direct internal dependency of https://github.com/cakephp/migrations and CakePHP apps. So how would this be affected by such a change? Right now, the benefit of this being...

https://github.com/cakephp/phinx/pull/2159 will make it possible to restore previous behavior for now We should also add docs on how to overcome those upgrading challenges however I agree, that we need some...

We might also want to add the details in docs and from release notes more like link to it.

Anyone wants to make a PR here? Otherwise we close this as this is a very old ticket.

So far CakePHP has never used enums as such, as they have a lot of disadvantages. Instead tinyint(2) and a PHP internal mapping has been used to better handle this...

Like I said: it would have to be a community PR As seen from other tickets: there is no big incentive for those topics to be addressed from maintainer side....

There is now a type for it: Binaryuuid see https://github.com/cakephp/phinx/pull/1734