News: Latest Additions and Pending Features
NOTICEIf you're still using
2.x framework version and desire documentation, go to
www2.lucinda-framework.com or, if still using
1.x, visit
old.lucinda-framework.com instead. Since neither will be developed on (except on bug fixing),
upgrade is strongly recommended!
What's New
What's New In Version 4.1
Code quality improvements suggested by matching apis code with popular code static analysis tools:
Recommendations were only followed if they provided a real positive improvement in code quality/readability (some, like adding
underscores at the beginning of private method names, are of very little value)!
What's New In Version 4.0
Purely aesthetic upgrade from version 3.3 (starts with same logic) mainly featuring:
- PHP 8.1+ compatible code
- actual enums wherever they were originally implemented as interfaces with constants
- usage of native Stringable class instead of developer defined one
- type hinting for ALL class fields, method parameters and return types thanks to:
Version 3.3 Available!
A new Console MVC API was created to handle console requests into responses + complete refactoring of Console API to feature a HTML-like templating engine for formatting console responses:
Version 3.3 Upgrade
Version 3.2 Available!
Classes referenced in XML for all APIs as well as classes in framework skeleton were required instead of being autoloaded. To enforce structural symmetry and ease of development, now ALL resources will be autoloaded regardless where they originate from:
Version 3.2 Upgrade
Version 3.1 Available!
MVC APIs in framework version 3.0 shared a significant amount of logic (namely everything about response rendering and the fundamentals behind application configuration). For that reason a new API had to be developed and framework needed to change too:
Version 3.1 Upgrade
What's New In Version 3.0
Framework has been upgraded to 3.0 version, featuring:
- PHP 7.1+ compatible code
- full PSR-4 compliance (incl. composer autoload)
- 100% unit test coverage for composing APIs
- development of new UnitTest API superior to PHPUnit in being simple, logical and super light weight
- making STDOUT MVC API event driven, using concepts similar to JavaScript
- development of new HTTP Headers API to encapsulate operations with HTTP headers according to RFC standards
- all composing APIs configure themselves by XML, instead of relying on Framework Engine API, in order to further reusability
- deprecation of HTTP Caching API in favor of a larger-scoped HTTP Headers API
- deprecation of Request Validation API in favor of a larger-scoped STDOUT MVC API
- code improvement, mostly in terms of achieving structural unity across all APIs
What's Planned
Following extra features are pending development:
