Change: Application directory changes #332

New issue

Closed

opened 2025-03-24 22:42:15 +00:00 by jamie · 4 comments

jamie commented

2025-03-24 22:42:15 +00:00

(Migrated from git.hazaar.io)

Problem Statement

The current version of Hazaar MVC uses application as the directory name for application code. In the new Hazaar Framework, this should be changed to app to provide a clear distinction between the two frameworks and align with modern conventions.

Who will benefit?

Developers using Hazaar Framework will have a shorter, more concise directory name.
It will help differentiate Hazaar Framework from Hazaar MVC.
New adopters may find app more intuitive and aligned with other frameworks.

Benefits and risks

Benefits:

Provides a clear distinction between Hazaar Framework and Hazaar MVC.
Aligns with naming conventions used by many modern frameworks.
Reduces verbosity in file paths.

Risks:

Requires migration steps for existing applications moving to Hazaar Framework.
May cause confusion for developers transitioning from Hazaar MVC.

Proposed solution

Update the default directory structure in Hazaar Framework to use app instead of application. Update documentation and tooling to reflect this change.

Examples

Laravel and Symfony both use app as the primary application directory.

Priority/Severity

High (This will bring a huge increase in performance/productivity/usability/legislative cover)
Medium (This will bring a good increase in performance/productivity/usability)
Low (anything else e.g., trivial, minor improvements)

## Problem Statement The current version of Hazaar MVC uses `application` as the directory name for application code. In the new Hazaar Framework, this should be changed to `app` to provide a clear distinction between the two frameworks and align with modern conventions. ## Who will benefit? - Developers using Hazaar Framework will have a shorter, more concise directory name. - It will help differentiate Hazaar Framework from Hazaar MVC. - New adopters may find `app` more intuitive and aligned with other frameworks. ## Benefits and risks ### Benefits: - Provides a clear distinction between Hazaar Framework and Hazaar MVC. - Aligns with naming conventions used by many modern frameworks. - Reduces verbosity in file paths. ### Risks: - Requires migration steps for existing applications moving to Hazaar Framework. - May cause confusion for developers transitioning from Hazaar MVC. ## Proposed solution Update the default directory structure in Hazaar Framework to use `app` instead of `application`. Update documentation and tooling to reflect this change. ## Examples - Laravel and Symfony both use `app` as the primary application directory. ## Priority/Severity - [x] High (This will bring a huge increase in performance/productivity/usability/legislative cover) - [ ] Medium (This will bring a good increase in performance/productivity/usability) - [ ] Low (anything else e.g., trivial, minor improvements)

jamie commented

2025-03-24 22:42:15 +00:00

(Migrated from git.hazaar.io)

assigned to @jamie

jamie commented

2025-03-25 10:27:17 +00:00

(Migrated from git.hazaar.io)

created branch 332-change-application-directory-changes to address this issue

created branch [`332-change-application-directory-changes`](/hazaar/framework/-/compare/master...332-change-application-directory-changes) to address this issue

jamie commented

2025-03-25 10:27:24 +00:00

(Migrated from git.hazaar.io)

mentioned in merge request !221