move clanCore modules for the external api #1583

Closed
opened 2024-06-06 10:02:59 +00:00 by kenji · 0 comments
Owner

Internally we like keeping the separation of concerns, but from the outside this can be confusing.

Suggestion:
Move clanCore modules inside of the clan namespace.
clanCore -> clan.core.
This way it is just as clear that there are core modules the clan modules depend on, but we don't introduce the overhead of two different toplevels.

Internally we like keeping the separation of concerns, but from the outside this can be confusing. Suggestion: Move clanCore modules inside of the clan namespace. `clanCore` -> `clan.core`. This way it is just as clear that there are core modules the clan modules depend on, but we don't introduce the overhead of two different toplevels.
kenji added the
enhancement
modules
labels 2024-06-06 10:02:59 +00:00
kenji added this to the Clan_Kanban_Board project 2024-06-06 10:02:59 +00:00
kenji closed this issue 2024-06-19 20:42:07 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
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: clan/clan-core#1583
No description provided.