a special syntax for contained rules

[tiye]

defstyle style-demo $ {}
  :& $ {}
    'contained "|some-rule-here"
    :color :red

to render:

some-rule-here {
  this-selector {
    color: red;
  }
}

Summary by CodeRabbit

• New Features

  • Introduced a new style rule for responsiveness targeting screens with a maximum width of 600 pixels.
  • Updated styling method to enhance modularity in component definitions.

• Bug Fixes

  • Incremented version numbers across multiple files to ensure compatibility with updated dependencies.

• Documentation

  • Updated versioning details in relevant files for clarity and consistency.

• Chores

  • Updated dependencies to their latest versions for improved performance and security.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to several configuration and code files, primarily focusing on version increments and style modifications. The GitHub Actions workflow configuration has been updated to use a newer version of the calcit-lang/setup-cr action. The compact.cirru file has seen enhancements in component style definitions and structure, including the introduction of a new defstyle macro. The deps.cirru file reflects a minor version update, while the package.json file includes several version changes for the overall package and its dependencies.

Changes

File	Change Summary
.github/workflows/tests.yaml	Updated calcit-lang/setup-cr action version from 0.0.7 to 0.0.8.
compact.cirru	Incremented version from 0.16.12 to 0.16.13. Updated component styles using :class-name, added defstyle macro, and modified function signatures.
deps.cirru	Updated :calcit-version from 0.9.5 to 0.9.6.
package.json	Incremented overall version from 0.16.12 to 0.16.16. Updated @calcit/procs from 0.9.5 to 0.9.6, and vite from ^5.4.7 to ^6.0.3.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHubActions
    participant App

    Developer->>GitHubActions: Push changes
    GitHubActions->>App: Run tests
    App-->>GitHubActions: Return test results
    GitHubActions-->>Developer: Notify results

Loading

---

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. (Experiment)
• @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]

Actionable comments posted: 6

📜 Review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

📥 Commits

Reviewing files that changed from the base of the PR and between 34ed45c and 5a63bc5.

⛔ Files ignored due to path filters (1)

• yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (5)

• .github/workflows/tests.yaml (1 hunks)
• calcit.cirru (7 hunks)
• compact.cirru (5 hunks)
• deps.cirru (1 hunks)
• package.json (1 hunks)

🔥 Files not summarized due to errors (1)

• calcit.cirru: Error: Server error: no LLM provider could handle the message

🔇 Additional comments (11)

calcit.cirru (3)

42-42: LGTM! Property rename improves clarity

The change from the previous property to :class-name makes the intention clearer.

---

131-141: LGTM! New defstyle implementation

The new defstyle macro implementation properly structures the style definition with support for contained rules.

---

197-210: LGTM! Required imports added

The necessary imports are properly added for the new styling system functionality.

compact.cirru (3)

3-3: Version update is appropriate.

The version number has been incremented from 0.16.12 to 0.16.13, which aligns with the updates in other files.

---

29-32: Implementation of 'contained' syntax looks correct.

The new 'contained' syntax within defstyle style-global appears to be correctly implemented, aligning with the PR's objective to introduce a syntax for contained rules.

---

934-936: Ensure robust handling of 'contained' rules in CSS generation.

The addition of logic to handle 'contained' rules in render-css-block seems appropriate. Verify that this implementation correctly handles all cases, including when contained is not present, to avoid potential runtime errors.

deps.cirru (1)

2-2: Version update is appropriate.

The :calcit-version has been updated from 0.9.5 to 0.9.6, aligning with dependency updates.

package.json (3)

2-2: Update package version appropriately.

The package version has been updated from 0.16.12 to 0.16.16.

---

4-4: Update dependency @calcit/procs to version 0.9.6.

The dependency version aligns with updates in deps.cirru.

---

11-11: Update vite to version ^6.0.3 and verify compatibility.

The development dependency vite has been updated. Ensure that the new version is compatible with the project and does not introduce breaking changes.

.github/workflows/tests.yaml (1)

20-20: Update GitHub Action calcit-lang/setup-cr to version 0.0.8.

The action version has been incremented. Verify that the new version functions as expected and does not introduce any unintended side effects in the CI workflow.