Breaking THE module into SUB modules #7

Open
opened 2025-06-10 14:53:35 +00:00 by orzklv · 0 comments
orzklv commented 2025-06-10 14:53:35 +00:00 (Migrated from github.com)

It worth to mention that all probable sub modules were written in a single file which would make maintenance quite hard for possible future maintainers, especially for those who are coming from totally beginner spectrum.

Therefore, following the existing #5 issue, it would be better to break it up into manageable and pluggable modules tied to a main parent module.

It worth to mention that all probable sub modules were written in a single file which would make maintenance quite _hard_ for possible future maintainers, especially for those who are coming from totally **beginner** spectrum. Therefore, following the existing #5 issue, it would be better to break it up into **manageable** and **pluggable** modules tied to **a main parent module**.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
uchar/infrastructure#7
No description provided.