Skip to content

Conversation

@mr-u0b0dy
Copy link
Contributor

@mr-u0b0dy mr-u0b0dy commented Jan 10, 2026

📑 Description

  • Add crazy-coverage.nvim plugin for displaying code coverage overlays

📖 Additional Information

  • Other coverage related plugin should be moved inside this category

- Add new coverage category
- Add crazy-coverage.nvim plugin for displaying code coverage overlays
@github-actions
Copy link

github-actions bot commented Jan 10, 2026

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).

Copy link
Member

@Uzaaft Uzaaft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong category. Move it to test category. And cleanup your code and the comments. Most of them arent needed.

The config call can me removed.
If the config you are passing is the default settings, just set it as an empty table.

@Uzaaft
Copy link
Member

Uzaaft commented Jan 10, 2026

Also tidy up your readme.md. Look at other readme's for inspiration. 1 line should be enough for the desc of the plugin.

@mr-u0b0dy
Copy link
Contributor Author

@Uzaaft I'll cleanup my code and readme.

I have a suggestion of creating new section for coverage. I'm currently in discussion(#2090) with the maintainers of
awesome-neovim to introduce this new section. I suppose the category here are based on awesome-neovim.

@Uzaaft
Copy link
Member

Uzaaft commented Jan 11, 2026

No its not. Its based off https://github.com/neurosnap/neovimcraft

@mr-u0b0dy
Copy link
Contributor Author

Ok but neovimcraft scraps awesome-neovim for tags.

@Uzaaft
Copy link
Member

Uzaaft commented Jan 12, 2026

Not gonna have a fight with you over this. I cleaned up the useless comments and moved it. Merging.

@Uzaaft Uzaaft changed the title feat(coverage): add crazy-coverage-nvim plugin feat(test): add crazy-coverage-nvim plugin Jan 12, 2026
@Uzaaft Uzaaft merged commit 83ca23d into AstroNvim:main Jan 12, 2026
23 of 24 checks passed
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