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

fix shikierror #185

Merged
merged 1 commit into from
Nov 23, 2024
Merged

fix shikierror #185

merged 1 commit into from
Nov 23, 2024

Conversation

Heesunni
Copy link
Contributor

@Heesunni Heesunni commented Nov 23, 2024

Closes #178

Summary by CodeRabbit

  • Bug Fixes
    • Improved the initialization process for the highlighter, ensuring themes and languages load correctly.
  • New Features
    • Enhanced control flow for rendering components, allowing for better handling of asynchronous loading of themes and languages.

Copy link

coderabbitai bot commented Nov 23, 2024

Walkthrough

The changes involve modifications to the cli/inbox/view.tsx file, specifically in the initialization process of the highlighter variable. The new implementation separates the loading of the theme and languages into distinct asynchronous calls, which alters the control flow of the component. The theme "github-light" and the languages "http" and "json" are now loaded individually, potentially impacting the rendering behavior of the component if the highlighter is not fully prepared before use.

Changes

File Change Summary
cli/inbox/view.tsx Modified highlighter initialization: separated theme and language loading into distinct asynchronous calls.

Suggested reviewers

  • dahlia

Poem

In the code where highlights gleam,
A rabbit hops, chasing a dream.
Themes and languages load anew,
Asynchronous magic, bright and true!
With every change, our flow will dance,
In this coding world, we take our chance! 🐇✨


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

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: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 96f725d and f90c45e.

📒 Files selected for processing (1)
  • cli/inbox/view.tsx (1 hunks)

Comment on lines +111 to +114
const highlighter = await getSingletonHighlighter();
await highlighter.loadTheme("github-light");
await highlighter.loadLanguage("http");
await highlighter.loadLanguage("json");
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Consider moving highlighter initialization into a lazy-loaded singleton pattern.

The current module-level initialization of the highlighter could block module loading. Consider refactoring to a lazy-loaded singleton pattern with proper error handling.

Here's a suggested implementation:

-const highlighter = await getSingletonHighlighter();
-await highlighter.loadTheme("github-light");
-await highlighter.loadLanguage("http");
-await highlighter.loadLanguage("json");
+let highlighterInstance: Awaited<ReturnType<typeof getSingletonHighlighter>> | null = null;
+
+async function getHighlighter() {
+  if (highlighterInstance) return highlighterInstance;
+  try {
+    highlighterInstance = await getSingletonHighlighter();
+    await highlighterInstance.loadTheme("github-light");
+    await Promise.all([
+      highlighterInstance.loadLanguage("http"),
+      highlighterInstance.loadLanguage("json")
+    ]);
+    return highlighterInstance;
+  } catch (error) {
+    console.error("Failed to initialize syntax highlighter:", error);
+    throw error;
+  }
+}

Then update the CodeBlock component to handle loading and error states:

 const CodeBlock: FC<CodeBlockProps> = ({ language, code }: CodeBlockProps) => {
+  const [html, setHtml] = useState<string | null>(null);
+  const [error, setError] = useState<Error | null>(null);
+
+  useEffect(() => {
+    async function highlight() {
+      try {
+        const highlighter = await getHighlighter();
+        const result = highlighter.codeToHtml(code, {
+          lang: language,
+          theme: "github-light",
+        });
+        setHtml(result);
+      } catch (e) {
+        setError(e instanceof Error ? e : new Error(String(e)));
+      }
+    }
+    highlight();
+  }, [code, language]);
+
+  if (error) {
+    return <div class="alert alert-danger m-3">Failed to highlight code: {error.message}</div>;
+  }
+  if (!html) {
+    return <div class="placeholder-glow m-3"><span class="placeholder col-12"></span></div>;
+  }
-  const result = highlighter.codeToHtml(code, {
-    lang: language,
-    theme: "github-light",
-  });
-  return <div dangerouslySetInnerHTML={{ __html: result }} class="m-3" />;
+  return <div dangerouslySetInnerHTML={{ __html: html }} class="m-3" />;
 };

Benefits:

  • Lazy loading prevents blocking module initialization
  • Parallel loading of languages improves performance
  • Proper error handling and loading states
  • Better user experience with loading indicators

Committable suggestion skipped: line range outside the PR's diff.

Copy link

codecov bot commented Nov 23, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.46%. Comparing base (18c5dd0) to head (f90c45e).
Report is 5 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #185   +/-   ##
=======================================
  Coverage   84.46%   84.46%           
=======================================
  Files          42       42           
  Lines       11618    11618           
  Branches     1157     1157           
=======================================
  Hits         9813     9813           
  Misses       1784     1784           
  Partials       21       21           

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


🚨 Try these New Features:

Copy link
Owner

@dahlia dahlia left a comment

Choose a reason for hiding this comment

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

Good job! Thanks for your contribution!

@dahlia dahlia merged commit cf3769f into dahlia:main Nov 23, 2024
12 checks passed
dahlia added a commit that referenced this pull request Nov 23, 2024
[ci skip]
dimsssss pushed a commit to dimsssss/fedify that referenced this pull request Nov 24, 2024
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.

fedify inbox throws a ShikiError during rendering web interface
2 participants