Skip to content

chore: willboosterify this repo #17

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

Merged
WillBooster-bot merged 1 commit into from
Apr 30, 2026
Merged

chore: willboosterify this repo #17

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@
__generated__/
@willbooster/
dist/
drizzle/mount/
temp/
tmp/
playwright-report/
Expand Down
4 changes: 4 additions & 0 deletions oxlint.config.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,7 @@
// wbfy:start oxlint-base
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot Apr 30, 2026

Choose a reason for hiding this comment

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

medium

The use of separate markers (oxlint-base and oxlint-export) for a simple two-line configuration file adds unnecessary noise. Unless required by the automation tool for specific injection points, consider merging these into a single block to simplify the file and reduce redundancy, as per Rule 6 of the repository style guide.

References
  1. Simplify code as much as possible to eliminate redundancy. (link)

import config from '@willbooster/oxlint-config';
// wbfy:end oxlint-base

// wbfy:start oxlint-export
export default config;
// wbfy:end oxlint-export
Loading