Conversation
…iant before now made its way to gii
…switch from snake_case to camelCase
|
Are we all aware that any customized templates, especially model//model.php in which the “old” array keys are used, will be “broken”? |
Yes, but i have no idea how to support backward compatibility for such a change. Maybe we can pin the gii version in the current master to 2.2.6 and make a 1.0.4 release of giiant and merge this pr after and make a 1.1.0 or even 2.0.0 release of giiant? |
|
Is the generated code different? In which way did it conflict (error) with gii 2.2.7? |
Key names of the getEnum "changed" from snake to camel case and overall the implementation in gii differs alot than the "original" in giiant. |
When generating a table with an enum field, the current giiant version(1.0.3) is not compatible with gii version 2.2.7 installed because the enum handling was included in the Gii through a pull request.
The problem is that this was implemented a little differently than it was originally implemented in giiant. see gii implementation vs original giiant implementation
This PR uses the naming from gii and adapts the corresponding places in the model template and raises the minimum giia constraint to 2.2.7
CC: @handcode