Repository navigation
Develop - #281
Merged
Merged
Develop#281
Conversation
…late-TypeScript into develop
…int rules Rewrite .github/CONTRIBUTING.md, which still described the unrelated rails_api_base project, with the tooling actually enforced here: EditorConfig defaults and per-language overrides, Oxlint configuration and notable rules, the recommended import order, Oxfmt options, Lefthook hooks, the Conventional Commits standard validated by commitlint, and the release rules from .releaserc.json. Add docs/linting.md registering every rule from the previous eslint.config.ts that was not carried over to .oxlintrc.json, split into three groups: stylistic rules now covered by Oxfmt or EditorConfig, rules with no Oxlint equivalent, and rules migrated under a different name. Rules with lost coverage include camelcase, no-invalid-this, spaced-comment, no-undef-init, wrap-iife, wrap-regex, the four eslint-plugin-security rules, import/order and import/no-extraneous-dependencies. Availability was verified against the rule registry shipped with oxlint 1.77.0. Register the new page in the mkdocs.yml nav. Signed-off-by: AlvaroDavi5 <alvaro-davi1@hotmail.com> Co-Authored-By: Claude <noreply@anthropic.com>
Rename .github/LICENSE.md to LICENSE.md and delete the duplicated LICENSE.txt, which carried the identical 21-line MIT text, so a single license file lives at the root where GitHub detects it. Signed-off-by: AlvaroDavi5 <alvaro-davi1@hotmail.com> Co-Authored-By: Claude <noreply@anthropic.com>
Run oxfmt over src, tests and scripts, which had never been formatted since the migration from ESLint and Prettier to the Oxc toolchain: 213 of the 220 matched files were failing `oxfmt --check`. The changes are purely cosmetic, driven by .oxfmtrc.json and .editorconfig — trailing commas, single-line bodies for short statements, collapsed blank lines and semicolons on type aliases. No logic, control flow or public signature was touched; `oxlint --deny-warnings` and `tsc --noEmit` were re-run clean afterwards. The commit hash is added to .git-blame-ignore-revs in the follow-up commit so this sweep does not obscure `git blame` history. Signed-off-by: AlvaroDavi5 <alvaro-davi1@hotmail.com> Co-Authored-By: Claude <noreply@anthropic.com>
Add .git-blame-ignore-revs pointing at the formatting-only commit that rewrote 213 files, so `git blame` keeps attributing those lines to the commits that changed their behaviour. GitHub picks the file up automatically; locally it requires `git config blame.ignoreRevsFile .git-blame-ignore-revs`, which is documented in the file header. Signed-off-by: AlvaroDavi5 <alvaro-davi1@hotmail.com> Co-Authored-By: Claude <noreply@anthropic.com>
…formatting DataParserHelper.toString falls back to String(data) for functions, which yields the function's own source text. The two assertions in the stringified-function test compared it against single-line literals, so they broke as soon as oxfmt expanded the inline function and arrow function into multiple lines. Collapse whitespace runs before comparing instead of pinning the expected value to a particular layout, which keeps the assertion checking what the helper returns while making it immune to future reformatting. Signed-off-by: AlvaroDavi5 <alvaro-davi1@hotmail.com> Co-Authored-By: Claude <noreply@anthropic.com>
…g files Run the formatter wired into the pre-commit hook over the Markdown, JSON and TypeScript files it had never touched: docs/, README, the .github templates and the .dev agent and instruction files, plus .oxfmtrc.json, .vscode/extensions.json, tsconfig.base.json, tsconfig.test.json and webpack.config.ts. Markdown changes are cosmetic only: table separators padded to column width, emphasis switched from asterisks to underscores, bullets normalised to dashes, thematic breaks switched from ___ to ---, and blank lines inserted around lists and headings. No prose was reworded. Config changes drop the trailing comma in .vscode/extensions.json, re-indent the block comment in tsconfig.base.json and collapse the single-entry webpack plugins array. Note that oxfmt strips the final newline from every JSON file it formats, which contradicts insert_final_newline in .editorconfig; the output is committed as produced by the tool and the conflict needs a follow-up decision. Signed-off-by: AlvaroDavi5 <alvaro-davi1@hotmail.com> Co-Authored-By: Claude <noreply@anthropic.com>
Register the formatting-only commit that reflowed the Markdown, JSON and TypeScript files outside src, so `git blame` keeps pointing at the commits that actually wrote that content. Signed-off-by: AlvaroDavi5 <alvaro-davi1@hotmail.com> Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PROJ-TASK_ID
Task Link
Task Description
...
Checklist
envsdirectory (if necessary)Justification for unselected checkboxes:
...
Evidence
Logs Link
