fix: resolve TypeScript errors in release-list component

[codeMaestro78]

No description provided.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
mlcli	Ready	Preview	Comment	Dec 7, 2025 9:28am

[Copilot]

Pull request overview

This PR resolves TypeScript errors in the release-list component by fixing type issues in the ReactMarkdown code component customization. The changes restructure how props are handled and add necessary type assertions to satisfy TypeScript's type checking.

Key Changes:

• Refactored props destructuring in the ReactMarkdown code component to avoid TypeScript errors
• Added type assertion for the oneDark style object to satisfy react-syntax-highlighter's type requirements
• Replaced the inline prop with computed isInline logic based on language match detection

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
website/tsconfig.tsbuildinfo	TypeScript build artifact updated after compilation
website/src/components/releases/release-list.tsx	Fixed TypeScript errors in code component by restructuring props handling and adding type assertion

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

[nitpick] The isInline variable and the condition !isInline && match could be simplified. Since isInline = !match, the condition !isInline && match is equivalent to just checking match. Consider simplifying to:

const match = /language-(\w+)/.exec(className || '');

return match ? (
  // block code with syntax highlighting
) : (
  // inline code
);

This makes the logic clearer and removes the unnecessary intermediate variable.

Suggested change

	const isInline = !match;
	return !isInline && match ? (
	return match ? (