Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Revert ":+1: Fix version of dependencies" #21

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 7, 2024
Merged

Revert ":+1: Fix version of dependencies" #21

merged 1 commit into from
May 7, 2024

Conversation

lambdalisue
Copy link
Owner

@lambdalisue lambdalisue commented May 7, 2024 •
edited by coderabbitai bot
Loading

This reverts commit 74d56e5.

Close #20

Summary by CodeRabbit

  • Refactor
    • Updated import paths across various modules to use a new protocol, enhancing the system's module resolution and reliability.

@coderabbitai coderabbitai
Copy link

coderabbitai bot commented May 7, 2024 •
edited
Loading

Walkthrough

The changes primarily involve updating import statements across several TypeScript files, switching from direct imports to using a "jsr:" prefix. This modification suggests a shift towards a different module resolution strategy or protocol, potentially to address issues related to module loading or namespace conflicts.

Changes

File Pattern Change Summary
bin/browse.ts, .../mod_test.ts,
.../bitbucket_org.ts, process_test.ts,
util_test.ts		 Updated import paths to use "jsr:" prefix for various modules.
deno.jsonc Removed several module imports.

Assessment against linked issues

Objective Addressed Explanation
git browse does not work (#20) ❓ It is unclear if the prefix "jsr:" resolves the import path issue mentioned.

🐰✨
A hop of faith in code we trust,
With every line, adjust we must.
From paths that break to paths that bind,
In "jsr:" prefix, solutions we find.
Cheers to changes, big and small,
In code's burrow, we tweak them all!
🌟🐇

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

@lambdalisue lambdalisue merged commit 6fb61f7 into main May 7, 2024
2 checks passed
@lambdalisue lambdalisue deleted the fix-jsr branch May 7, 2024 17:29
coderabbitai[bot]
coderabbitai bot reviewed May 7, 2024
View reviewed changes
Copy link

@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

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between b169e2c and 78a81c4.
Files selected for processing (6)
  • bin/browse.ts (1 hunks)
  • deno.jsonc (1 hunks)
  • hosting_service/mod_test.ts (1 hunks)
  • hosting_service/services/bitbucket_org.ts (1 hunks)
  • process_test.ts (1 hunks)
  • util_test.ts (1 hunks)
Files skipped from review due to trivial changes (2)
  • bin/browse.ts
  • deno.jsonc
Additional comments not posted (4)
process_test.ts (1)

1-1: Ensure the "jsr:" prefix in the import statement is correctly configured in the Deno environment.

hosting_service/services/bitbucket_org.ts (1)

3-3: Ensure the "jsr:" prefix in the import statement is correctly configured in the Deno environment.

hosting_service/mod_test.ts (1)

1-2: Ensure the "jsr:" prefix in the import statements is correctly configured in the Deno environment.

util_test.ts (1)

1-2: Ensure the "jsr:" prefix in the import statements is correctly configured in the Deno environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

git browse does not work
1 participant
@lambdalisue