Skip to content

Conversation

@rawnly
Copy link
Contributor

@rawnly rawnly commented Jun 12, 2025

📑 Description

This solves a problem where lazy could not resolve dependency if it was already installed in user configuration (see video below)

CleanShot.2025-06-13.at.00.31.04.mp4

This solves a problem where lazy could not resolve dependency if it was
already installed in user configuration
@github-actions
Copy link

github-actions bot commented Jun 12, 2025

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

  • If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

  • If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

  • Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

  • README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

  • Entry returns a single plugin spec with the new plugin as the only top level spec (not applicable for recipes or packs).

  • Proper usage of opts table rather than setting things up with the config function.

  • Proper usage of specs table for all specs that are not dependencies of a given plugin (not applicable for recipes or packs).

@rawnly rawnly changed the title chore: rename schemastore to be lowercase fix(packs.json/packs.yaml): rename schemastore to be lowercase Jun 12, 2025
@rawnly rawnly changed the title fix(packs.json/packs.yaml): rename schemastore to be lowercase fix(pack/json): rename schemastore to be lowercase Jun 13, 2025
@Uzaaft
Copy link
Member

Uzaaft commented Jun 14, 2025

@rawnly Could you split this PR into two? One for json and one for yaml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants