These are the features and issues that don't need to be resolved before we start on CodeIgniter 4 ... most will be resolved as part of the development of other features, or raised as issues/PRs during development. This thread conveys our thoughts and decisions...
We welcome your comments, but please stay on topic! This thread is about the CI4 features that we don't need decisions for until it comes time to start building that version. If you try to hijack the thread, or post non-relevant items that should be or that are dealt with elsewhere, your posts will be deleted without notice. We may post additional comments in fgeature/issue specific threads.
Code generation tool: handled by tool outside of core framework. Not part of core framework.
Community input: mixed.
Service layer support: unclear. Seems outside CI design principles.
Community input: mixed.
Input filtering / form validation: beyond what we have, no. Thru third party package, easily integrated: +1.
Community input: mixed.
Entity models: Not ORM! might be a good idea.
Community input: mixed.
More base models: Might be a good idea, but better handled thru external packages. Not part of core framework.
Community input: mixed.
Multiple DB support: Beyond the core, no. Handle thru packages/extensions. Not part of core framework.
Community input: mixed.
Redo homepage design: sure. Not part of core framework.
Community input: 76% in favor.
Redo website design: ??. It could make sense for CI4 vs CI3. Would have to encompass forum too. Not part of core framework.
Community input: 73% in favor.
Conclusion: do it when closer to release.
Remove index.php: Need better tutorials, not default removal.
Community feedback: 51% in favor
Better/more tutorials: absolutely, but not part of core framework.
Community feedback: 77% in favor.
Package/plugins site: good idea, but not part of core framework.
Community input: overwhelmingly in favor.
Target audience: everyone. Keep it simple, lean & useful.
Community input: all over the map.
User guide translations: awkward to accommodate.
Community input: mixed.
Multiple file uploads: specific issue; deal with at implementation
Community input: mixed.
Shopping cart support: one size doesn't suit all; use external package
James Parry
Project Lead
