Conversation
Co-Authored-By: jaseel0 <225665919+jaseel0@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
naheel0
added
ci/cd
|
@copilot can fill the error for me Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect). C:\Users\Dell\Desktop\New folder\open source\ReadmeGenAI\src\components\Generator\MarkdownPreview.tsx:15:5
|
[WIP] Add preview option to existing feature
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughAdds an autofix GitHub Actions workflow, a .prettierignore, Markdown rendering and preview/code toggle in the MarkdownPreview component, new markdown-related deps, removes a Vitest config and a test file, and updates package.json scripts/dependencies. Changes
Sequence Diagram(s)sequenceDiagram
participant PR as "Pull Request"
participant GH as "GitHub Actions (autofix.yml)"
participant Runner as "Ubuntu Runner"
participant Node as "Node.js/npm"
participant Formatter as "Prettier / ESLint"
participant Action as "autofix-ci/action@v1"
PR->>GH: open PR / push to main (trigger)
GH->>Runner: start job (autofix)
Runner->>Node: setup Node (LTS), npm cache
Runner->>Node: run npm ci
Runner->>Formatter: run Prettier on file globs
Formatter-->>Runner: files possibly modified
Runner->>Formatter: run ESLint --fix on src/**/*
Formatter-->>Runner: files possibly modified
Runner->>Action: run autofix-ci/action@v1 (always)
Action-->>GH: report results / push fixes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@copilot fix it for me Error: Calling setState synchronously within an effect can trigger cascading renders Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following:
Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect). C:\Users\Dell\Desktop\New folder\open source\ReadmeGenAI\src\components\Generator\MarkdownPreview.tsx:15:5
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Fix all issues with AI agents
In @.github/workflows/autofix.yml:
- Line 30: Replace the deprecated --ext usage in the CI workflow command `npx
eslint src --ext .ts,.tsx --fix` with an explicit glob pattern so ESLint runs
across TypeScript files on all v9 versions; update the command to target files
via a glob like src/**/*.{ts,tsx} (retain the --fix flag) to ensure
compatibility with flat config and unpinned ESLint versions.
In `@src/components/Generator/MarkdownPreview.tsx`:
- Around line 18-22: The handleCopy function calls navigator.clipboard.writeText
without error handling; wrap that call in a try/catch inside handleCopy so you
only call setCopied(true) on success and catch any exceptions from
navigator.clipboard.writeText(content), log or surface the error (e.g.,
console.error or show a toast), and ensure copied state is reset
(setCopied(false)) in the error path or finally as appropriate; reference
handleCopy, navigator.clipboard.writeText, content, and setCopied when making
the change.
- Around line 12-16: The mounted state and useEffect in the MarkdownPreview
component cause an ESLint pipeline failure and a hydration mismatch; remove the
mounted state variable, the setMounted(true) useEffect, and any conditional
rendering that checks mounted in MarkdownPreview so the component renders
identically on server and client, and if you need to avoid SSR for ReactMarkdown
import it with next/dynamic({ ssr: false }) at the import site (refer to the
MarkdownPreview component, the mounted state/useEffect and any ReactMarkdown
usage to locate the changes).
- Around line 76-81: The ReactMarkdown usage renders raw HTML via rehypeRaw
without sanitization; import rehypeSanitize from 'rehype-sanitize' and add it to
the rehypePlugins array after rehypeRaw in the MarkdownPreview component (where
ReactMarkdown, remarkGfm, rehypeRaw and content are used) so the plugins become
[rehypeRaw, rehypeSanitize] and the AI-generated content is sanitized before
rendering.
🧹 Nitpick comments (4)
package.json (1)
9-9: Test script removed but test dependencies remain.The
"test"script was removed, yetvitest,@vitest/coverage-v8,@testing-library/jest-dom, and@testing-library/reactare still listed indevDependencies(lines 26–27, 31, 36). If testing is being dropped, clean up these dependencies to avoid confusion and unnecessary installs..github/workflows/autofix.yml (1)
3-6: Consider restrictingpull_requesttrigger to specific branches.Currently the workflow triggers on all pull requests regardless of target branch. If this is intentional (autofix on all PRs), that's fine — just noting it runs on every PR across the repo.
src/components/Generator/MarkdownPreview.tsx (2)
28-50: Prefer Tailwindproseclasses over global styled JSX.You already have
@tailwindcss/typographyas a dependency. Usingproseutility classes on the container would replace all of these manual style rules, be more maintainable, and avoid global style pollution fromjsx global.
6-6: Remove leftover dev comment// Add this.
| npx prettier --write "src/**/*.{ts,tsx,js,jsx,json,css,md}" "public/**/*" "*.{js,ts,json,md}" --ignore-unknown | ||
|
|
||
| # ESLint targets your source code logic | ||
| npx eslint src --ext .ts,.tsx --fix |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
ESLint v9 --ext flag removed migration guide
💡 Result:
Why --ext “disappeared” in ESLint v9
With flat config (eslint.config.js, default in v9), ESLint originally rejected --ext (you’d see “Invalid option '--ext' … you’re using eslint.config.js”). (github.com)
The intended replacement was to use files globs in your flat config. (npmjs.com)
Migration (recommended): replace --ext with files in eslint.config.js
If you previously had something like:
npx eslint --ext .ts,.tsx .Remove --ext and add a “selector” object near the top of eslint.config.js:
// eslint.config.js
export default [
{ files: ["**/*.ts", "**/*.tsx"] },
// ...the rest of your config objects
];Then run:
npx eslint .This is the approach documented by the ESLint config migrator (@eslint/migrate-config). (npmjs.com)
If you must use --ext from the CLI (no config file)
ESLint v9.21.0 reintroduced --ext specifically to support linting arbitrary extensions without a config file, shown together with --no-config-lookup. (eslint.org)
Example:
npx eslint --no-config-lookup --rule '{"no-unused-vars":"error"}' --ext '.jsx'Citations:
- 1: Providing non-default extensions via CLI. eslint/eslint#18521
- 2: https://www.npmjs.com/package/%40eslint/migrate-config?utm_source=openai
- 3: https://www.npmjs.com/package/%40eslint/migrate-config?utm_source=openai
- 4: https://eslint.org/blog/2025/02/eslint-v9.21.0-released/
- 5: https://eslint.org/blog/2025/02/eslint-v9.21.0-released/
🏁 Script executed:
# Check ESLint version in the repository
find . -type f \( -name "package.json" -o -name "package-lock.json" -o -name "yarn.lock" \) -not -path "*/node_modules/*" | head -5Repository: BeyteFlow/ReadmeGenAI
Length of output: 99
🏁 Script executed:
# Check for ESLint configuration files
find . -type f \( -name ".eslintrc*" -o -name "eslint.config.*" \) | head -10Repository: BeyteFlow/ReadmeGenAI
Length of output: 84
🏁 Script executed:
cat package.json | grep -A 2 -B 2 "eslint"Repository: BeyteFlow/ReadmeGenAI
Length of output: 341
🏁 Script executed:
cat eslint.config.mjsRepository: BeyteFlow/ReadmeGenAI
Length of output: 529
Use glob pattern instead of deprecated --ext flag.
ESLint v9 initially removed the --ext flag with flat config support. While the flag was reintroduced in v9.21.0, since the version is unpinned (^9), using an explicit glob pattern ensures compatibility across all v9 versions and is the recommended approach with flat config.
Proposed fix
- npx eslint src --ext .ts,.tsx --fix
+ npx eslint "src/**/*.{ts,tsx}" --fix📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| npx eslint src --ext .ts,.tsx --fix | |
| npx eslint "src/**/*.{ts,tsx}" --fix |
🤖 Prompt for AI Agents
In @.github/workflows/autofix.yml at line 30, Replace the deprecated --ext usage
in the CI workflow command `npx eslint src --ext .ts,.tsx --fix` with an
explicit glob pattern so ESLint runs across TypeScript files on all v9 versions;
update the command to target files via a glob like src/**/*.{ts,tsx} (retain the
--fix flag) to ensure compatibility with flat config and unpinned ESLint
versions.
Co-authored-by: naheel0 <191262736+naheel0@users.noreply.github.com>
[WIP] Add preview option to enhance user experience
|
@copilot In fix it |
Co-authored-by: naheel0 <191262736+naheel0@users.noreply.github.com>
Add HTML sanitization and error handling to MarkdownPreview
🚀 BΞYTΞFLʘW | Pull Request Protocol
PR Type: (Choose one:
feat|fix|refactor|docs|perf)Issue Link: Fixes #
📝 System Summary
Provide a concise brief of the changes introduced to the stream.
🛠️ Technical Changes
.........🧪 Quality Assurance (QA)
npm run buildexecuted without errors.🖼️ Visual Evidence
If this PR affects the UI, drop a screenshot or GIF below:
📡 Developer Authorization
Authorized by: @naheel0
Timestamp: {{ 12/2/2026 }}