Update flake.nix: changed URL literals to strings

[dot-file]

URL literals cause confusion as they use the same x:x syntax as lambdas. The use of these is considered to be a bad practice. Apart from that, Lix which is a Nix fork dropped the support of this feature with its 2.92 release making building of Lumen with it result in an error.

Summary by CodeRabbit

• Chores
  • Standardized dependency URL declarations in build configuration by converting them to quoted strings for consistency with tooling and future maintenance.
• Style
  • Applied minor formatting adjustments to configuration to align with style conventions.
• Release Impact
  • No user-facing changes or functional impact; builds and behavior remain unchanged.

[coderabbitai]

Walkthrough

Quoted the nix flake input URLs in flake.nix by changing unquoted tokens to string literals for nixpkgs.url and flake-utils.url. No other logic or outputs were modified.

Changes

Cohort / File(s)	Summary
Flake input URL quoting flake.nix	Converted inputs.nixpkgs.url and inputs.flake-utils.url from unquoted tokens to quoted strings; URLs unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled quotes on paths so neat,
Two tiny strings now tied up sweet.
No streams were moved, no branches bent—
Just tidier trails where inputs went.
Hop hop! The flake feels more complete. 🥕

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between d3d067c and de12e93.

📒 Files selected for processing (1)

• flake.nix (1 hunks)

🔇 Additional comments (1)

flake.nix (1)

5-6: Flake URL literals properly quoted

All flake URL references are already quoted in flake.nix, and a repository-wide scan found no unquoted URL literals remaining. No further changes needed.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.