Skip to content

Conversation

@thedavidmeister
Copy link
Contributor

@thedavidmeister thedavidmeister commented Sep 8, 2025

Motivation

Solution

Checks

By submitting this for review, I'm confirming I've done the following:

  • made this PR as small as possible
  • unit-tested any new functionality
  • linked any relevant issues or PRs
  • included screenshots (if this involves a front-end change)

Summary by CodeRabbit

  • Chores

    • Updated license headers across source and test files to reflect the current organization name.
    • No changes to functionality, interfaces, or behavior.
  • Documentation

    • Refreshed copyright notices in file headers for consistency and accuracy.
  • Tests

    • Test files updated only for header metadata; no test logic changes.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 8, 2025

Walkthrough

Updated SPDX FileCopyrightText headers across error, library, and test files to attribute "Rain Open Source Software Ltd" instead of "thedavidmeister". No functional, interface, or behavioral changes.

Changes

Cohort / File(s) Summary of Changes
Error headers
src/error/ErrDecimalFloat.sol, src/error/ErrParse.sol
Updated SPDX copyright header text only.
Lib decimal float headers
src/lib/format/LibFormatDecimalFloat.sol, src/lib/parse/LibParseDecimalFloat.sol
Updated SPDX copyright header text only.
Test headers
test/src/lib/format/LibFormatDecimalFloat.countSigFigs.t.sol, test/src/lib/format/LibFormatDecimalFloat.toDecimalString.t.sol
Updated SPDX copyright header text only.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch 2025-09-08-copyright

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 6

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3df76ef and 334b386.

📒 Files selected for processing (6)
  • src/error/ErrDecimalFloat.sol (1 hunks)
  • src/error/ErrParse.sol (1 hunks)
  • src/lib/format/LibFormatDecimalFloat.sol (1 hunks)
  • src/lib/parse/LibParseDecimalFloat.sol (1 hunks)
  • test/src/lib/format/LibFormatDecimalFloat.countSigFigs.t.sol (1 hunks)
  • test/src/lib/format/LibFormatDecimalFloat.toDecimalString.t.sol (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)
  • GitHub Check: rainix (ubuntu-latest, rainix-sol-legal)
  • GitHub Check: rainix (ubuntu-latest, rainix-sol-static)
  • GitHub Check: rainix (macos-latest, rainix-rs-test)
  • GitHub Check: rainix (ubuntu-latest, test-wasm-build)
  • GitHub Check: rainix (ubuntu-latest, rainix-rs-static)
  • GitHub Check: rainix (macos-latest, rainix-sol-legal)
  • GitHub Check: rainix (ubuntu-latest, rainix-rs-test)
  • GitHub Check: rainix (ubuntu-latest, rainix-sol-test)
  • GitHub Check: git-clean
🔇 Additional comments (1)
src/lib/format/LibFormatDecimalFloat.sol (1)

2-2: SPDX headers verified and up to date. No old attributions remain; every .sol file includes the updated SPDX-FileCopyrightText and a SPDX-License-Identifier line.

@@ -1,5 +1,5 @@
// SPDX-License-Identifier: LicenseRef-DCL-1.0
// SPDX-FileCopyrightText: Copyright (c) 2020 thedavidmeister
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
Copy link
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

LGTM on attribution.

Same optional note about year range if applicable.

-// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
+// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
📝 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.

Suggested change
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
🤖 Prompt for AI Agents
In src/error/ErrDecimalFloat.sol around line 2 the SPDX copyright attribution is
acceptable as-is, but optionally update the SPDX-FileCopyrightText to include an
explicit year or year range (e.g., "2020-2025" or "2020") if your project policy
requires a year range; change the string accordingly and commit the updated SPDX
header, otherwise leave the line unchanged since the reviewer approved it.

@@ -1,5 +1,5 @@
// SPDX-License-Identifier: LicenseRef-DCL-1.0
// SPDX-FileCopyrightText: Copyright (c) 2020 thedavidmeister
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
Copy link
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Attribution updated correctly.

Consider a year range if contributions continued beyond 2020.

-// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
+// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
📝 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.

Suggested change
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
🤖 Prompt for AI Agents
In src/error/ErrParse.sol around line 2, the SPDX copyright header currently
lists a single year (2020); update it to a year range reflecting continued
contributions (for example "2020-2025" or "2020-present") to correctly attribute
ongoing work, and ensure the SPDX line remains a single-line comment starting
with "// SPDX-FileCopyrightText:" followed by the chosen year range and the
original owner string.

@@ -1,5 +1,5 @@
// SPDX-License-Identifier: LicenseRef-DCL-1.0
// SPDX-FileCopyrightText: Copyright (c) 2020 thedavidmeister
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
Copy link
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

SPDX copyright holder update looks good.

Consider updating the year to a range if contributions continued after 2020.

Apply if appropriate:

-// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
+// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
📝 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.

Suggested change
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
🤖 Prompt for AI Agents
In src/lib/format/LibFormatDecimalFloat.sol around line 2, the SPDX copyright
header uses a single year (2020); update it to a year range to reflect continued
contributions (e.g., 2020-2025) by replacing the line with the same SPDX header
but with the appropriate end year range for Rain Open Source Software Ltd —
adjust the end year to the latest contribution year and keep the SPDX header
format unchanged.

@@ -1,5 +1,5 @@
// SPDX-License-Identifier: LicenseRef-DCL-1.0
// SPDX-FileCopyrightText: Copyright (c) 2020 thedavidmeister
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
Copy link
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Header owner change approved.

Apply year range if the file saw commits after 2020.

-// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
+// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
📝 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.

Suggested change
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
🤖 Prompt for AI Agents
In src/lib/parse/LibParseDecimalFloat.sol around line 2, the SPDX copyright
header was changed and needs a year range if the file has commits after 2020;
determine the file's last commit year (e.g., via git log -1 --format=%ad
--date=format:%Y) and update the SPDX header to use a year range from 2020 to
that year (e.g., 2020-2025) while keeping the owner as Rain Open Source Software
Ltd.

@@ -1,5 +1,5 @@
// SPDX-License-Identifier: LicenseRef-DCL-1.0
// SPDX-FileCopyrightText: Copyright (c) 2020 thedavidmeister
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
Copy link
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Header change acknowledged.

If work spans multiple years, use a year range for accuracy.

-// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
+// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
📝 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.

Suggested change
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
🤖 Prompt for AI Agents
In test/src/lib/format/LibFormatDecimalFloat.countSigFigs.t.sol around line 2,
the SPDX header lists a single year ("2020"); update it to a year range to
reflect multi-year work (for example "2020-2025" or "2020-<current year>") so
the copyright span is accurate; replace the single-year token with the
appropriate start–end range in the SPDX header.

@@ -1,5 +1,5 @@
// SPDX-License-Identifier: LicenseRef-DCL-1.0
// SPDX-FileCopyrightText: Copyright (c) 2020 thedavidmeister
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
Copy link
Contributor

Choose a reason for hiding this comment

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

🧹 Nitpick (assertive)

Consistent with the PR intent.

Optional: adjust to a year range for precision.

-// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
+// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
📝 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.

Suggested change
// SPDX-FileCopyrightText: Copyright (c) 2020 Rain Open Source Software Ltd
// SPDX-FileCopyrightText: Copyright (c) 2020-2025 Rain Open Source Software Ltd
🤖 Prompt for AI Agents
In test/src/lib/format/LibFormatDecimalFloat.toDecimalString.t.sol around line
2, the SPDX copyright header currently lists a single year; update it to a year
range for greater precision (e.g., "2020-2025" or the current year) by replacing
the single year with an inclusive range in the SPDX-FileCopyrightText line.

@thedavidmeister thedavidmeister merged commit 9e87b24 into main Sep 8, 2025
10 checks passed
@github-actions
Copy link

github-actions bot commented Sep 8, 2025

@coderabbitai assess this PR size classification for the totality of the PR with the following criterias and report it in your comment:

S/M/L PR Classification Guidelines:

This guide helps classify merged pull requests by effort and complexity rather than just line count. The goal is to assess the difficulty and scope of changes after they have been completed.

Small (S)

Characteristics:

  • Simple bug fixes, typos, or minor refactoring
  • Single-purpose changes affecting 1-2 files
  • Documentation updates
  • Configuration tweaks
  • Changes that require minimal context to review

Review Effort: Would have taken 5-10 minutes

Examples:

  • Fix typo in variable name
  • Update README with new instructions
  • Adjust configuration values
  • Simple one-line bug fixes
  • Import statement cleanup

Medium (M)

Characteristics:

  • Feature additions or enhancements
  • Refactoring that touches multiple files but maintains existing behavior
  • Breaking changes with backward compatibility
  • Changes requiring some domain knowledge to review

Review Effort: Would have taken 15-30 minutes

Examples:

  • Add new feature or component
  • Refactor common utility functions
  • Update dependencies with minor breaking changes
  • Add new component with tests
  • Performance optimizations
  • More complex bug fixes

Large (L)

Characteristics:

  • Major feature implementations
  • Breaking changes or API redesigns
  • Complex refactoring across multiple modules
  • New architectural patterns or significant design changes
  • Changes requiring deep context and multiple review rounds

Review Effort: Would have taken 45+ minutes

Examples:

  • Complete new feature with frontend/backend changes
  • Protocol upgrades or breaking changes
  • Major architectural refactoring
  • Framework or technology upgrades

Additional Factors to Consider

When deciding between sizes, also consider:

  • Test coverage impact: More comprehensive test changes lean toward larger classification
  • Risk level: Changes to critical systems bump up a size category
  • Team familiarity: Novel patterns or technologies increase complexity

Notes:

  • the assessment must be for the totality of the PR, that means comparing the base branch to the last commit of the PR
  • the assessment output must be exactly one of: S, M or L (single-line comment) in format of: SIZE={S/M/L}
  • do not include any additional text, only the size classification
  • your assessment comment must not include tips or additional sections
  • do NOT tag me or anyone else on your comment

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 8, 2025

Oops, something went wrong! Please try again later. 🐰 💔

@coderabbitai coderabbitai bot mentioned this pull request Feb 10, 2026
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant