Update sentry sample rate

[shhdgit]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
website-docs	Error			Nov 21, 2025 7:28am

[gemini-code-assist]

Summary of Changes

Hello @shhdgit, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on refining application stability, performance, and robustness. It includes an adjustment to the Sentry tracing sample rate to manage monitoring overhead, introduces a safety check for DOM node removal to prevent errors, and implements optional chaining for more resilient property access in navigation and filtering logic. Additionally, a useEffect hook's execution timing was updated for consistent rendering behavior in a tab component.

Highlights

• Sentry Sample Rate Adjustment: The Sentry tracing sample rate has been reduced from 0.1 to 0.01, which will decrease the volume of traces sent to Sentry and potentially optimize monitoring costs.
• Enhanced DOM Manipulation Safety: A defensive check was added before removing a DOM node in the Contributors component to ensure the node is still a child of its parent, preventing potential runtime errors if the node has already been detached.
• Robust Property Access with Optional Chaining: Optional chaining (?.) has been introduced in RightNav.tsx and filterRightToc.ts when accessing nested items properties, making the code more resilient to null or undefined intermediate objects.
• Updated useEffect Hook Behavior: A useEffect hook in SimpleTab.tsx was modified by removing its dependency array, causing it to run on every render. This ensures the onRendered(id) callback is consistently invoked.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the Sentry tracesSampleRate to reduce the volume of traces being sent. It also includes several small fixes and improvements across different components.

My review focuses on improving code quality and efficiency:

• In Contributors/index.tsx, I've suggested a simpler way to remove the DOM node.
• In SimpleTab.tsx, I've identified an inefficient useEffect implementation and provided a detailed suggestion for a more performant solution using useCallback and a proper dependency array. This is the most important feedback in this review.
• For RightNav.tsx and filterRightToc.ts, I've noted some unnecessary optional chaining that could be simplified.

Overall, the changes are good, but the suggested refactoring for the useEffect in SimpleTab is recommended to avoid potential performance issues.

[gemini-code-assist]

Removing the dependency array from useEffect causes it to run after every render, which is inefficient. This was likely done to fix a linting warning about missing dependencies.

A better approach is to specify the dependencies. For this useEffect, the dependencies are id and onRendered.

However, simply adding [id, onRendered] will cause the effect to run on every render if onRendered is a new function on each render of the parent SimpleTab component.

To fix this correctly, you should wrap the onRendered prop's creation in the SimpleTab component with useCallback. This will memoize the function and ensure the useEffect in TabContentDetector only runs when id or the memoized onRendered function actually changes.

Here's how you can apply this in SimpleTab.tsx:

// In SimpleTab component
const onRenderedCallback = React.useCallback((id: string) => {
  setRenderedTabs((prev) => {
    if (prev.includes(id)) {
      return prev;
    }
    // Add the new tab and then sort based on actualTabs order
    const newTabs = [...prev, id];
    return newTabs.sort((a, b) => {
      const aIndex = actualTabs.findIndex(
        (tab) => (tab.props?.value || tab.props.label) === a
      );
      const bIndex = actualTabs.findIndex(
        (tab) => (tab.props?.value || tab.props.label) === b
      );
      return aIndex - bIndex;
    });
  });
}, [actualTabs]);

// ... then in the return statement of SimpleTab, pass onRenderedCallback
<TabContentDetector
  // ...
  onRendered={onRenderedCallback}
>
  {child}
</TabContentDetector>

Then, you can update this useEffect as suggested.

Suggested change

	if (
	}, [id, onRendered]);

[gemini-code-assist]

While this check is more robust and correctly prevents an error if the node is not a child of its parent, you can simplify this logic by using the .remove() method on the DOM element. It achieves the same goal of removing the node from its parent without throwing an error if the node has no parent, and it's more concise.

Suggested change

	// Check if the node is still a child of its parent before removing
	if (
	appendedNode.parentNode &&
	appendedNode.parentNode.contains(appendedNode)
	) {
	appendedNode.parentNode.removeChild(appendedNode);
	}
	appendedNode.remove();

[gemini-code-assist]

The optional chaining on item here is not necessary. item is an element from the items array being iterated over with forEach, and it's not expected to be null or undefined in this context. The original code if (item.items) was sufficient and slightly cleaner.

Suggested change

	if (item?.items) {
	if (item.items) {

[gemini-code-assist]

Similar to another change in this PR, the optional chaining on item is not necessary here. item is an element from the items array being iterated over with .map(), and it's not expected to be null or undefined at this point in the function. The original code was sufficient.

Suggested change

	if (item?.items && item.items.length > 0) {
	if (item.items && item.items.length > 0) {