• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Features That are missing right now

#1
[Template Engine]
Options: Jade/Blade
Should be optional
So that we can write the view page more object oriented

[Faker Library]
Option For Mysql,SQL, etx
N/A
If this library is loaded than it's already connected to database and it can see the colomn types (INT|FLOAT|VARCHAR) and can generate fake data according to user input choice 

[Authentication Library]
Options Ion_auth
Optional
I sometime use's the ion_auth lib just incase I want to finish my project quick. But there should a Lib for that purpose. Coz every Crud need's this kind of functionality


I love CI and due to it's simplicity and those who says laravel  Dodgy best are not actually good developers, they don't understand the word FREEDOM in programming.

Note to developers: Please never stop working on this Open Source Framework. There are so many developer's like me who are entirely dependent on CI and TEAM <3 <3
Reply

#2
You can add all of that yourself, it would just bloat CI and make it run slower!
What did you Try? What did you Get? What did you Expect?

Joined the CodeIgniter Community in 2009.          ( Skype: insitfx )
Reply

#3
Although I know that some of the features will never be added to CI, I am curious how many CI apps in production don't have features like auth, middleware, orm...
Codeigniter is simply one of the tools you need to learn to be a successful developer. Always add more tools to your coding arsenal!
Reply

#4
In all of the apps I've written once in CodeIgniter, I've never used middleware or an ORM, though most have had an auth of one sort or another.

Instead:

- middleware was replaced with an AuthController that would ensure the user was logged in and had permissions
- Query builder and well named methods in the model were enough.

That's not to say those features aren't nice when you have them, but since CI hasn't had them - people still get by. And in some ways, it's all a bit more explicit and simple to follow along.
Support Development  • Practical CodeIgniter 3  • Vulcan - CLI Tools for CI4
Reply

#5
(02-28-2018, 02:37 PM)kilishan Wrote: In all of the apps I've written once in CodeIgniter, I've never used middleware or an ORM, though most have had an auth of one sort or another.

Instead:

- middleware was replaced with an AuthController that would ensure the user was logged in and had permissions
- Query builder and well named methods in the model were enough.

That's not to say those features aren't nice when you have them, but since CI hasn't had them - people still get by. And in some ways, it's all a bit more explicit and simple to follow along.

Interesting. I'm ok with it not being included in CI as it doesn't really affect me but I'd be generally curious to get a broader view of what CI users do.

Let's just say for examples sake that 95% of CI users install an ORM right after they setup a CI application, it would be interesting to see how CI could help the community.

Anyways, like I said, it really doesn't change anything for me, but it would settle my curiosity. The few CI applications I still manage (I've mostly migrated to Laravel and Node, but my biggest app is in CI) all use an ORM, Auth, a 3rd party migration tool (I like Phinx), a date library (Carbon), and vlucas/phpdotenv. But it's easy enough for me to add those myself.
Codeigniter is simply one of the tools you need to learn to be a successful developer. Always add more tools to your coding arsenal!
Reply

#6
(02-28-2018, 11:47 PM)albertleao Wrote: Interesting. I'm ok with it not being included in CI as it doesn't really affect me but I'd be generally curious to get a broader view of what CI users do.

Let's just say for examples sake that 95% of CI users install an ORM right after they setup a CI application, it would be interesting to see how CI could help the community.

Anyways, like I said, it really doesn't change anything for me, but it would settle my curiosity. The few CI applications I still manage (I've mostly migrated to Laravel and Node, but my biggest app is in CI) all use an ORM, Auth, a 3rd party migration tool (I like Phinx), a date library (Carbon), and vlucas/phpdotenv. But it's easy enough for me to add those myself.

That would be interesting to see. On the plus side, dotenv and a date library come out of the box in CI4. What is it about Phinx that makes you prefer that for migrations?
Support Development  • Practical CodeIgniter 3  • Vulcan - CLI Tools for CI4
Reply

#7
(03-01-2018, 07:13 AM)kilishan Wrote: That would be interesting to see. On the plus side, dotenv and a date library come out of the box in CI4. What is it about Phinx that makes you prefer that for migrations?

I was a fan of having a CLI option built right out of the box and wasn't too fond of CI 3s migration tool. Phinx was easy to install, easy to incorporate in my deployment methods (Jenkins, CodePipeline, AWS ElasticBeanstalk), and most of all is updated on a pretty consistent basis. 

I usually get met with pitch forks whenever I mention Laravel on this forum, but the primary reason I've migrated to Laravel is the same reason I use phinx. The speed in which new features are added and bugs are fixed is alarmingly fast. I know that usually means that the upgrade path to Laravel is tougher than in CI, but that's because we unfortunately only have you, Narf, and a handful of others able to keep development going at a decent pace. And honestly, I've never had any issues with 'speed' due to Laravels bloated size nor have I had to spend lots of time upgrading.

I do look forward to CI 4 and would love to upgrade my largest application to it when it's reached 1.0. I just hope that the upgrade path isn't as painful as it was to go from Laravel 4 to 5.
Codeigniter is simply one of the tools you need to learn to be a successful developer. Always add more tools to your coding arsenal!
Reply

#8
An AUTH Module [Official] is a necessary one. 90% CI apps will use an auth if it include a CRUD. so +100 for adding an official AUTH Module.

ORM and Middleware are a bit bloat. Good models and good query builder class will server the purpose.

A templating engine is an optional one. from the side of optimisation and speed templating engine add another slowdown layer. Still we can write PHP Tags in HTML.
Codeigniter Fan. --
Reply

#9
I don't use an ORM on any of my designs, nor do I want to be forced to use a default AUTH package. Yes, I do use AUTH in my work, but I get to choose which one and that can change, depending on the project.

Rather than relying on CI to pick one choice, YOU get to make the choice. I like that philosophy.
CI 3.1 Linux Mint 18.3 xfce Apache 5.x  Mysql 5.x PHP 5.x PHP 7.x
Remember: Obfuscation is a bad thing.
Clarity is desirable over Brevity every time.
Reply


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2018 MyBB Group.