| CodeIgniter v4.0.5 and v4.1.0 released |
Thanks, paulbalandan!
Modifiled file list except system/. Code: 4.0.5/LICENSE(02-01-2021, 08:06 PM)kenjis Wrote: Thanks, paulbalandan!Thanks so much!
Wow.. First of all let me thank everyone involved for the update. I've been expecting this for quite some time.
However I believe its not only me that's a bit disappointed about the files that have actually changed. One of the best features of previous versions was that updating usually only wanted the replacement of the system folder. Too many changes in the App/Config folder this time - most of them purely cosmetic - this makes everyone NOT using composer spend quite some time updating. Why was this needed? Going this route - why not put the App/Config folder in the system itself, and force us to only rely on .env file? I know that's been discussed in the forums, and i don't mean to be disrespectful but i think that this is not a good idea. And no, "use composer" is not always the answer to all questions  On the bright side - can we get some more clarity on the new BaseModel since its not documented? Should we keep extending Model or should we extend BaseModel?
@korgoth Just to be clear: Composer only handles the equivalent of the **syestem** folder. Users installing via Composer methods will need to update files in the **app** folder the same as everyone else.
The team has worked very hard at not allowing any breaking changes. This means: nothing in **app** needs to be updated. Are there new versions of files in **app**, and is there some benefit to implementing them? Yes, and we are working on documenting those but the bottom line is: no major version, no breaking changes. Re: BaseModel... splitting Model into its new class and BaseModel was to make room for future development on "NoSQL" databases. The current model had some restrictions by assuming a SQL-type database, so keeping those in place and going everything else to an abstract class gives us more room for future development. If you are a current user of the framework: keep using Model per usual, no changes necessary. You can consider this an "internal change" unless you've been dabbling in NoSQL databases for CodeIgniter 4.
Yes, most files in the modified file list is just because comment style was changed.
So you don't need to update them. And nothing is broken, even if you don't update any files in other than system/. As for updating files other than system/, it is exactly the same as CI3. However, it is true that CI4 is young and still has many minor changes. Whether you use Composer or not, the situation is the same.
Upgrade success
One command hehe Thanks CI Teams and Composer v2 Learning CI4 from my works, from errors and how to fix bugs in the community Love CI & Thanks CI Teams |
| Welcome Guest, Not a member yet? Register Sign In |
MENU
EXTRA MENU
ABOUT US
CodeIgniter is a powerful PHP framework with a very small footprint, built for developers who need a simple and elegant toolkit to create full-featured web applications.
