Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add force build; handle cjk displaying #247

Merged
merged 2 commits into from
Jun 27, 2024
Merged

add force build; handle cjk displaying #247

merged 2 commits into from
Jun 27, 2024

Conversation

tiye
Copy link
Member

@tiye tiye commented Jun 26, 2024

No description provided.

@tiye tiye requested a review from a team June 26, 2024 18:59
Copy link
Contributor

coderabbitai bot commented Jun 26, 2024

Walkthrough

This update primarily involves version increments in multiple configuration files (Cargo.toml, package.json) and the addition of new test assertions. It also introduces logic to handle build scripts in src/bin/calcit_deps.rs and updates string formatting behavior in src/calcit.rs. A subtle modification in ts-src/js-tuple.mts changes a function argument to alter toString behavior.

Changes

Files Summary of Changes
Cargo.toml, package.json Updated version numbers from 0.8.58 to 0.8.59 and updated dependency version of cirru_edn.
calcit/test-string.cirru Introduced a new assertion for special characters and escape handling in string manipulation tests.
src/bin/calcit_deps.rs Added logic to check and run build.sh script if present during specific conditions in handle_path.
src/calcit.rs Modified fmt::Display for Calcit to handle string escaping based on simplicity criteria.
ts-src/js-tuple.mts Changed the second argument of the toString function call from false to true in CalcitTuple.

Poem

In version's dance, we mark anew,
Dependencies aligned, and tests we brew.
A script is run, if found, to build,
With escaping strings that won't be stilled.
Tuple's true face now revealed,
In Calcit's lands, the changes sealed.
🌀✨🐇


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Outside diff range and nitpick comments (1)
src/bin/calcit_deps.rs (1)

Line range hint 142-160: New build script execution logic introduced.

The addition of logic to execute a build.sh script if present is a significant enhancement. Ensure that the script execution is secure and does not allow arbitrary code execution vulnerabilities.

Would you like me to help generate unit tests for this new functionality to ensure its robustness and security?

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9b9f080 and a4f4d56.

Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
Files selected for processing (6)
  • Cargo.toml (2 hunks)
  • calcit/test-string.cirru (1 hunks)
  • package.json (1 hunks)
  • src/bin/calcit_deps.rs (5 hunks)
  • src/calcit.rs (2 hunks)
  • ts-src/js-tuple.mts (1 hunks)
Files skipped from review due to trivial changes (3)
  • Cargo.toml
  • calcit/test-string.cirru
  • package.json
Additional comments not posted (2)
ts-src/js-tuple.mts (1)

62-62: Change in toString method argument approved.

The change from false to true in the toString method's second argument indicates a deliberate alteration in how strings are constructed. Make sure this change aligns with the intended string formatting behavior in the application.

Verification successful

Change in toString method argument approved.

The search results confirm that the toString method is consistently used with the updated argument signature across multiple files. This indicates that the change from false to true in the toString method's second argument is deliberate and consistent with the intended string formatting behavior in the application.

  • Verified locations:
    • ts-src/js-tuple.mts
    • ts-src/js-record.mts
    • ts-src/js-map.mts
    • ts-src/js-cirru.mts
    • ts-src/js-set.mts
    • ts-src/custom-formatter.mts
    • ts-src/calcit.procs.mts
    • ts-src/js-list.mts
    • ts-src/calcit-data.mts
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify that the change in the `toString` method does not introduce any unintended side effects.

# Test: Search for the function usage. Expect: Only occurances of the new signature.
rg --type typescript $'toString'

Length of output: 66



Script:

#!/bin/bash
# Description: Verify that the change in the `toString` method does not introduce any unintended side effects.

# Test: Search for the function usage. Expect: Only occurrences of the new signature.
rg --type ts 'toString' -A 3 -B 3

Length of output: 182



Script:

#!/bin/bash
# Description: Debug why `rg` is not searching any files and verify the presence of `.ts` files.

# Step 1: Check for the presence of `.ts` files in the repository.
echo "Checking for .ts files in the repository..."
fd -e ts

# Step 2: Debug the `rg` command to understand why files are being skipped.
echo "Debugging rg command..."
rg --type ts 'toString' -A 3 -B 3 --debug

Length of output: 19241



Script:

#!/bin/bash
# Description: Verify that the change in the `toString` method does not introduce any unintended side effects.

# Test: Search for the function usage. Expect: Only occurrences of the new signature.
rg 'toString' -g '*.ts' -g '*.mts' -A 3 -B 3

Length of output: 19648

src/calcit.rs (1)

124-133: Updated string formatting logic in Calcit::fmt.

The use of cirru_edn::is_simple_char() to conditionally escape characters is a robust approach to handle string escaping. Confirm that this new logic correctly handles all edge cases and improves the readability and correctness of the output.

@csvwolf csvwolf merged commit 7dae7b4 into main Jun 27, 2024
2 checks passed
@csvwolf csvwolf deleted the force-build branch June 27, 2024 03:38
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