Commits
Click on a commit to change the comparison rangefeat: re-add rust-toolchain.toml file
Re-added rust-toolchain.toml that was accidentally deleted during branch operations.
Uses Rust 1.89.0 channel with default profile as specified in main branch.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com> fix: merge upstream release changes and resolve conflicts
Merged latest upstream changes including:
- oxfmt v0.1.0 release updates
- Disabled Windows failing test
- Updated changelogs and version numbers
Resolved conflict by removing test snapshot that was disabled upstream.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com> test: update formatter TypeScript snapshot
Updated test results showing current performance:
- TypeScript formatter: 8247/8816 (93.55%)
All other test suites passing with stable results.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com> fix(linter): enforce func-names "never" config for recursive functions
Previously, the func-names rule was incorrectly allowing named function expressions when they were recursive, even when the config was set to "never". This was a deviation from ESLint's behavior.
This change fixes the rule to correctly flag ALL named function expressions when config is "never", including recursive ones. The recursive function exception now only applies to "always" and "as-needed" configs where the name is actually needed.
Changes:
- Modified the recursive function check to only apply for "always" and "as-needed" configs
- When config is "never", all named function expressions are now flagged as errors
- Updated test expectations to reflect correct behavior
This aligns with ESLint's implementation where "never" means no names are allowed on function expressions, regardless of whether they need the name for recursion.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>