move clanCore modules for the external api #1583
Labels
No Label
backups
blog
bootstrapping
bug
changes-requested
cli
documentation
duplicate
enhancement
facts
help wanted
invalid
Inventory
low_prio
manager
modules
needs-review
networking
packaging
question
secrets
template
test
tooling
user-testing
vm
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: clan/clan-core#1583
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.