Skip to content

Conversation

@ascandone
Copy link
Contributor

@ascandone ascandone commented Mar 3, 2025

conflicts with main got out of hand, pr was moved here: #44

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 3, 2025

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


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

@codecov
Copy link

codecov bot commented Mar 3, 2025

Codecov Report

Attention: Patch coverage is 83.07509% with 142 lines in your changes missing coverage. Please review.

Project coverage is 63.14%. Comparing base (ae202e9) to head (8191cd5).
Report is 13 commits behind head on main.

Files with missing lines Patch % Lines
internal/parser/antlrParser/numscript_parser.go 79.86% 81 Missing and 10 partials ⚠️
internal/parser/ast.go 0.00% 29 Missing ⚠️
internal/interpreter/evaluate_expr.go 70.00% 7 Missing and 2 partials ⚠️
internal/parser/parser.go 91.56% 7 Missing ⚠️
...rnal/parser/antlrParser/numscript_base_listener.go 0.00% 4 Missing ⚠️
internal/interpreter/interpreter_error.go 0.00% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #43      +/-   ##
==========================================
- Coverage   63.27%   63.14%   -0.14%     
==========================================
  Files          29       29              
  Lines        6462     6723     +261     
==========================================
+ Hits         4089     4245     +156     
- Misses       2191     2287      +96     
- Partials      182      191       +9     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

fix, finally

renamed antlr module

quick and dirty, but wrong

maybe we're almost there

impl account interpolation

run diagnostic on interp str

fix stupid pointers error
@ascandone ascandone force-pushed the feat/experimental-interpolation-syntax branch from d19ce58 to 8191cd5 Compare March 4, 2025 10:21
@ascandone ascandone closed this Mar 4, 2025
@ascandone ascandone deleted the feat/experimental-interpolation-syntax branch March 4, 2025 14:03
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