Release/v0.1.7

[metaboulie]

📝 Summary

🔍 Description of Changes

Type of Change

• Bug fix
• New feature
• New command
• New theme
• Breaking change
• Documentation update

Checklist

• I have tested these changes
• I have updated documentation
• My code follows project guidelines

📜 Reviewers

@metaboulie

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Refined internal configuration and updated the application version.
• Documentation
  • Improved CLI help texts for clearer command parameter descriptions.
• New Features
  • Launched a new Gruvbox theme offering an extensive, adaptive color scheme and enhanced visual styling.

Walkthrough

This pull request updates configuration and documentation files. The linter configuration in ruff.toml is modified to exclude both the tests directory and sample.py. The Marimo theme manager’s version is incremented from 0.1.6 to 0.1.7, and the CLI documentation is refined to accurately describe the behavior of the git_ignore parameter. Additionally, a new CSS file is added for the Gruvbox theme, defining a comprehensive set of CSS variables for styling.

Changes

File(s)	Change Summary
ruff.toml	Updated the exclude configuration from ["tests"] to ["tests", "sample.py"].
src/motheme/__init__.py, src/motheme/cli.py	Bumped version from 0.1.6 to 0.1.7 in __init__.py and updated the git_ignore parameter docstring in cli.py to clarify its intended behavior.
themes/gruvbox/gruvbox.css	Added a new CSS file that defines a comprehensive set of CSS variables for the Gruvbox theme, including fonts, colors, shadows, and layout properties.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2d7fdf0 and 58ff8f7.

📒 Files selected for processing (4)

• ruff.toml (1 hunks)
• src/motheme/__init__.py (1 hunks)
• src/motheme/cli.py (3 hunks)
• themes/gruvbox/gruvbox.css (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: windows-latest / Py 3.12
• GitHub Check: windows-latest / Py 3.11
• GitHub Check: windows-latest / Py 3.10
• GitHub Check: windows-latest / Py 3.9

🔇 Additional comments (6)

src/motheme/__init__.py (1)

3-3: Version update correctly implements semantic versioning.

The increment from version 0.1.6 to 0.1.7 follows proper semantic versioning protocols, indicating a minor update with backward compatibility.

ruff.toml (1)

1-1: Appropriate linter exclusion update.

The addition of "sample.py" to the exclude list is appropriate. This prevents linting rules from being applied to what is likely a demonstration file.

src/motheme/cli.py (3)

50-50: Documentation accuracy improvement.

The revised description more precisely explains the git_ignore parameter's behavior. "Files that are not tracked by git" is more accurate than "files that are git ignored", as git-ignored files are often a subset of untracked files.

---

78-78: Documentation consistency maintained.

The updated parameter description matches the correction made in the apply function, maintaining consistency across the codebase.

---

105-105: Documentation consistency continued.

The parameter description update is consistently applied across all three functions, ensuring uniform documentation.

themes/gruvbox/gruvbox.css (1)

1-107: Well-structured Gruvbox theme implementation.

The CSS implementation provides a comprehensive color palette with clear organization:

• Font variables with appropriate fallbacks
• Systematic color organization (dark, light, bright, neutral, faded)
• Semantic color mapping for UI states
• Proper use of light-dark() function for theme switching

The implementation follows best practices in CSS variable naming and organization.

✨ Finishing Touches

• 🔥 Error while generating docstrings. (♻️ Check again to generate again)

---

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.
• @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.

[coderabbitai]

Note

All docstrings were kept as they were. No new docstrings were generated.