update 2025 02 03

[NobbZ]

• adjust attribute names
• nvim-crates: update
• nvim-gitsigns: update
• nvim-indent-blankline: update
• nvim-leap: update
• nvim-lspconfig: update
• nvim-lz-n: update
• nvim-nio: update
• nvim-none-ls: update
• nvim-notify: update
• nvim-rainbow: update
• nvim-startuptime: update
• nvim-trouble: update
• nvim-which-key: update

Summary by CodeRabbit

• Refactor

  • Updated naming conventions for internal keys to enhance consistency.

• Chore

  • Refreshed underlying dependency sources to incorporate the latest upstream improvements, ensuring enhanced performance and stability.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates key naming conventions in a Nix expression and refreshes dependency versioning data. In bin/default.nix, camelCase keys in both the packages and checks sections are renamed to kebab-case. In npins/sources.json, several Git repository entries (including those for neovim and related plugins) have their revision, url, and hash fields updated to new values.

Changes

File(s)	Change Summary
bin/default.nix	Renamed keys in packages and checks sections: addPlugin → add-plugin, updateNvim → update-nvim, and updatePlugins → update-plugins.
npins/sources.json	Updated versioning details for multiple entries (e.g., neovim, nvim-gitsigns, nvim-indent-blankline, nvim-leap, nvim-lspconfig, nvim-nio, nvim-none-ls, nvim-notify, nvim-rainbow, nvim-startuptime, nvim-trouble, nvim-which-key) with new revision, url, and hash values.

Possibly related PRs

• update 2025 01 20 #13: Involves similar renaming in key configurations and corresponding updates in dependency revisions for the neovim entry.

Poem

In a burrow of code I hop along,
Renamed keys now sing a kebab song.
Versions updated with a gentle tweak,
Dependencies refreshed, solutions unique.
I, a rabbit of CodeRabbit delight,
Celebrate changes in the moonlit night! 🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ac2c9bd and e235a59.

📒 Files selected for processing (2)

• bin/default.nix (1 hunks)
• npins/sources.json (13 hunks)

✅ Files skipped from review due to trivial changes (1)

• bin/default.nix

🔇 Additional comments (12)

npins/sources.json (12)

35-37: Neovim Plugin Revision Update:
The “neovim” entry’s revision, url, and hash have been updated to point to the new commit (87e806186c721f12c338af86677b6d1e6e2fa44a). This update is consistent with the objective of refreshing the plugin versions. Please ensure that this change is tested against any integrations relying on the neovim API.

---

71-73: nvim-gitsigns Plugin Revision Update:
The updated revision, url, and hash for the “nvim-gitsigns” entry correctly reflect the new version (9b36d497495436c135659902054ee637e0ba6021). Verify that the updated version maintains compatibility with your existing git integration settings in Neovim.

---

83-85: nvim-indent-blankline Revision Update:
The changes for “nvim-indent-blankline” update its revision, url, and hash to the latest commit (e10626f7fcd51ccd56d7ffc00883ba7e0aa28f78). This aligns with the overall update effort. Ensure that any configuration or display adjustments required by the updated version are addressed.

---

95-97: nvim-leap Plugin Revision Update:
The “nvim-leap” entry now reflects a new revision, url, and hash (be8e6eee2dabc68ce810ddf2e800c14bfda09fee). Confirm that the new version does not introduce breaking changes in how leap-based motions are configured or used.

---

107-109: nvim-lspconfig Revision Update:
The updates to the “nvim-lspconfig” entry—with a new revision (00b236b795acfb79339bd6771488c155073a2889), URL, and hash—ensure that the latest plugin version is used. Please verify that the LSP configurations remain fully operational with this upstream update.

---

215-217: nvim-nio Revision Update:
The “nvim-nio” section now uses an updated set of revision, url, and hash values (21f5324bfac14e22ba26553caf69ec76ae8a7662). Ensure that this new version integrates seamlessly with your Neovim test setups and configurations.

---

242-244: nvim-none-ls Revision Update:
For “nvim-none-ls”, the updated revision, url, and hash reflect the new version (ed8f80849ef1ad31c2f74679fafdef7801091247). Make sure that any changes in the plugin’s API or behavior are accommodated in your configuration.

---

254-256: nvim-notify Plugin Revision Update:
The change to the “nvim-notify” entry—with its new revision, url, and hash (22f29093eae7785773ee9d543f8750348b1a195c)—updates the plugin to the latest version. It is recommended to test the plugin’s notification behavior after this update.

---

305-307: nvim-rainbow Plugin Revision Update:
The updated revision, URL, and hash for “nvim-rainbow” (cf0da2516b0684596b09c51dbc93c609cdc2f455) ensure that the plugin now pulls from the most recent commit on GitLab. Please verify that delimiter highlighting and related features work as expected.

---

317-319: nvim-startuptime Revision Update:
The “nvim-startuptime” entry now points to a new commit (9aaa3c0880e63a8934ba58a430c6139225bba238) as reflected by the updated revision, URL, and hash. Confirm that performance measurement and startup time logging remain accurate following this update.

---

365-367: nvim-trouble Plugin Revision Update:
The revision, URL, and hash for “nvim-trouble” have been updated (6f380b8826fb819c752c8fd7daaee9ef96d4c689). Please ensure that the troubleshooting features provided by this plugin continue to function correctly in the updated version.

---

377-379: nvim-which-key Plugin Revision Update:
The updated values for the “nvim-which-key” entry (revision 0e76a87ac51772569aec678dc74baa8e2a86100c, new URL, and hash) bring in the latest version of which-key.nvim. Test key mapping previews to confirm that they are displayed correctly post-update.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.