Library re-integration

Summary

The current structure of Hazaar MVC with separate libraries (hazaar-common, hazaar-dbi, hazaar-warlock, hazaar-parser) introduces unnecessary complexity and fragmentation. To simplify the framework and improve maintainability, it is proposed to re-integrate all Hazaar MVC libraries into the core library. Additionally, the hazaar-forms library will be deprecated, and ownership will be transferred to APIR Systems Limited.

Area of the system

The change will impact the structure and organization of the Hazaar MVC framework and related libraries.

How does this currently work?

Currently, Hazaar MVC consists of separate libraries (hazaar-common, hazaar-dbi, hazaar-warlock, hazaar-parser) that are used alongside the core library. The hazaar-forms library is also a part of the ecosystem.

What is the desired way of working?

The desired way of working involves the following changes:

1. Re-integrate the functionality of hazaar-common, hazaar-dbi, hazaar-warlock, and hazaar-parser into the core Hazaar MVC library. This consolidation will simplify the framework and reduce unnecessary dependencies.
2. Deprecate the hazaar-forms library and transfer ownership to APIR Systems Limited. This ensures ongoing maintenance and support for hazaar-forms under their management.
3. Update the core Hazaar MVC library to include the functionality previously provided by the separate libraries.
4. Provide migration guides and documentation to assist existing users in transitioning from the separate libraries to the integrated core library.
5. Communicate the deprecation and ownership transfer of hazaar-forms to the Hazaar MVC community and encourage them to utilize suitable alternatives.

Priority/Severity

• High (This change will simplify the framework, improve maintainability, and align the library structure)
• Medium (This change will enhance the framework's organization and reduce complexity)
• Low (Considered a minor improvement, not critical for functionality)