packspec
packspec copied to clipboard
neovim
ALPHA package dependencies spec
The field descriptions use `packspec` as the keyword in the schema. The examples use `specification_version`. My 2 cents is I dislike `specification_version` as not being intent specific enough. I prefer...
A somewhat common thing to do is having post-install hooks. Maybe it could be included in the spec? A couple of ideas for the syntax (not 100% sure about the...
A bit of CI to update the docs, and also update the readme with the new fields I added. The workflow will update the code blocks we have as examples...
### Problem When I hear dependency I think of something third party thingy and putting `neovim` identifier inside it _maybe_ is not a great idea. As this is **the** editor...
Maybe plugins should have some standard way of accessing versions of their dependencies to handle differences in API and behavior between versions? Example: ```lua packspec["telescope"].version -- returns a string, eg....
```lua -- Usage: local path = vim.dep "plenary.path" ``` Implementation: ```lua -- instead of deps, we can call it `lua_modules` :cry: -- -- TODO: Add `deps` stuff to `package.path` so...
Some dependencies are runtime, some are build time. The specification may want to distinguish these, as the latter could cause the plugin to fail installation.
- [x] write some guidance for required/optional features of implementers - [x] Settle on name `packagespec`, `plugspec` and updated the `package_specification` field and the documentation - [x] Provide a section...
The way I see it there are a couple problems with the current `dependencies` format. First, special dependencies like `neovim`. I assume the implementation is supposed to just have special...