refactor(init): clarify public helper ownership #553
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
fugitive
good first issue
help wanted
invalid
question
v0.1.0
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
barrettruth/forge.nvim!553
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refactor/public-submodule-boundaries-549"
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?
Problem
The root
require('forge')surface still bundled helper-style exports whose owning public facades already existed elsewhere, and the:Forgecommand implementation still exposed a flat set of internalcmd_*modules at the root oflua/forge/.Solution
Turn
lua/forge/init.luainto a thinner assembly layer by aliasing helper exports directly fromforge.pr,forge.issue,forge.repo,forge.format, andforge.review; moverepo_info()ontoforge.repo; document the owning helper modules in the help file; add a focused spec that locks the root compatibility shims to those owners; and move the internal command parser, completion, dispatch, and resolver helpers underlua/forge/cmd/while keepingrequire('forge.cmd')stable viacmd/init.lua.Closes #549
Closes #550