fix(import): added support of importing spec-files directly#30
Merged
Conversation
Contributor
Author
|
use-case is like that: (it is my current dotfiles, commited version is still on lazy, and I'm trying to migrate it to zpack keeping plugins structure, and also temporary commenting some imports (so it gives possibility to import just few specs, and not a whole dir: return {
{ import = "plugins.ui-ux.colorschemes", }, -- ColorSchemes
-- { import = "plugins.ui-ux.bars", }, -- Bars ("Panels", "Lines")
-- { import = "plugins.ui-ux.ux", }, -- General UI/UX Reworkinng
-- { import = "plugins.ui-ux.syntax", },
} |
Owner
|
Looks good. Thank you for the contribution! |
zuqini
added a commit
that referenced
this pull request
Jun 15, 2026
PR #30 added single-file import (import = 'plugins.foo' resolving lua/plugins/foo.lua) but landed without tests or docs. This adds: - tests for the single-file path, file-over-directory precedence, and enabled=false gating on a single-file import - a code comment making the file-shadows-directory precedence intentional - vimdoc (doc/zpack.txt) coverage of the single-file form and precedence - README + docs/spec.md coverage of the file-over-directory precedence - guaranteed restoration of mocked vim.fn.stdpath / vim.uv.fs_stat in the test harness teardown, so an assertion failure mid-test no longer leaks the mock into later tests Closes zpack_nvim-thi
zuqini
added a commit
that referenced
this pull request
Jun 15, 2026
PR #30 added single-file import (import = 'plugins.foo' resolving lua/plugins/foo.lua) but landed without tests or docs. This adds: - tests for the single-file path, file-over-directory precedence, and enabled=false gating on a single-file import - a code comment making the file-shadows-directory precedence intentional - vimdoc (doc/zpack.txt) coverage of the single-file form and precedence - README + docs/spec.md coverage of the file-over-directory precedence - guaranteed restoration of mocked vim.fn.stdpath / vim.uv.fs_stat in the test harness teardown, so an assertion failure mid-test no longer leaks the mock into later tests Closes zpack_nvim-thi
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(as it was done in lazy.nvim)