• 2 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5

(07-16-2017, 11:30 PM)sv3tli0 Wrote: Wouldn't it be nice if we remove that .php from the name of ci.php ? (as simple as possible)

We have already the env php at the start so in most cases it will work and without calling the php command before the file.. 
#!/usr/bin/env php

"ci" shouldn't be used, so either "CI" or "[c|C]ode[i|I]gniter" or even "ignite/r" ..
This way people will only have to write CI <command> (or max php CI <command>).

I had planned on removing the extension at some point, but hadn't yet looked into the implications on Windows machines, and any other possible conflicts. It's been a decade since I've worked on Windows enough to remember how that would affect things.

What you don't mention is why ci shouldn't be used. Ignite comes across as either cheesy or cocky depending on my mood that day (and yes, it's one that I considered), but the only contradiction I could see with ci was continuous integration, which wouldn't matter whether it was lower or uppercase. And I don't recall ever seeing any CLI function that was named in uppercase, so I think that idea's out.
Practical CodeIgniter 3  • CodeIgniter 4 Foundations - Coming Soon • Vulcan - CLI Tools for CI4

Messages In This Thread
[CI4] CLI - by marksman - 12-09-2016, 06:25 PM
RE: [CI4] CLI - by kilishan - 12-12-2016, 10:08 PM
RE: [CI4] CLI - by humni - 07-16-2017, 03:58 PM
RE: [CI4] CLI - by kilishan - 07-16-2017, 09:51 PM
RE: [CI4] CLI - by sv3tli0 - 07-16-2017, 11:30 PM
RE: [CI4] CLI - by kilishan - 07-17-2017, 07:27 AM
RE: [CI4] CLI - by sv3tli0 - 07-17-2017, 11:10 PM

Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  

Users browsing this thread:
1 Guest(s)

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