Skip to content
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.

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

TRST-R-4 Remove unused LicenseRegistry.setExpireTime() function #166

Merged
merged 4 commits into from
Jun 27, 2024

Conversation

Ramarti
Copy link

@Ramarti Ramarti commented Jun 14, 2024

Remove LicenseRegistry setExpireTime since it's not used.

Summary by CodeRabbit

  • New Features

    • Introduced LicenseRegistryHarness (only used in tests) to mock license expiration time starts, while removing setExpireTime.
  • Bug Fixes

    • Improved the reliability of expiration checks within license management tests.
  • Refactor

    • Removed redundant setExpireTime function from ILicenseRegistry.
    • Updated tests to utilize LicenseRegistryHarness for setting expiration time.
  • Tests

    • Enhanced test coverage by integrating LicenseRegistryHarness into license expiration scenarios.

Copy link

coderabbitai bot commented Jun 14, 2024

Walkthrough

The recent changes primarily revolve around transitioning the functionality of setting expiration times from the ILicenseRegistry interface to a new mock contract, LicenseRegistryHarness. The ILicenseRegistry has had the setExpireTime function removed, while the added LicenseRegistryHarness contract allows setting expiration times for licenses for testing purposes. Additionally, associated test files have been updated to incorporate these changes and ensure the functionality remains intact through the new LicenseRegistryHarness methods.


Changes

File Path Summary
contracts/interfaces/registries/ILicenseRegistry.sol Removed the setExpireTime function.
test/foundry/mocks/module/LicenseRegistryHarness.sol Added new contract LicenseRegistryHarness with a constructor and setExpirationTime function.
test/foundry/registries/LicenseRegistry.t.sol Removed old test for setExpireTime and updated tests to use LicenseRegistryHarness for setting expiration.
test/foundry/utils/BaseTest.t.sol Added import for LicenseRegistryHarness and initialized lrHarnessImpl with an instance of LicenseRegistryHarness.

Sequence Diagram(s)

sequenceDiagram
    participant Test as Test Suite
    participant Harness as LicenseRegistryHarness
    participant Registry as LicenseRegistry

    Test->>Harness: setExpirationTime(ipId, expireTime)
    Harness->>Registry: call set expiration logic
    Registry->>Harness: expiration set confirmed
    Harness->>Test: expiration set confirmed
Loading

Poem

In the world of contracts, code refined,
A rabbit's joy, new paths aligned. 🐇
Expiry time, now set with grace,
In Harness’ arms, a better place.
Tests revamped, so sleek and true,
Cheers to updates, old ‘n new! 🎉


Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@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: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b2b1e82 and cdd42b4.

Files selected for processing (1)
  • contracts/registries/LicenseRegistry.sol (1 hunks)

@Ramarti Ramarti changed the title Remove unused method TRST-R-4 Remove unused LicenseRegistry.setExpireTime() function Jun 14, 2024
Copy link

@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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between cdd42b4 and 3ac27f5.

Files selected for processing (4)
  • contracts/interfaces/registries/ILicenseRegistry.sol (1 hunks)
  • test/foundry/mocks/module/LicenseRegistryHarness.sol (1 hunks)
  • test/foundry/registries/LicenseRegistry.t.sol (7 hunks)
  • test/foundry/utils/BaseTest.t.sol (3 hunks)
Additional comments not posted (3)
test/foundry/mocks/module/LicenseRegistryHarness.sol (1)

6-12: The implementation of LicenseRegistryHarness extends LicenseRegistry and introduces a new method setExpirationTime. This method directly interacts with a presumably internal function _setExpirationTime, which is not shown here. Ensure that the internal function properly handles permissions and state changes securely.

contracts/interfaces/registries/ILicenseRegistry.sol (1)

Line range hint 1-1: The removal of setExpireTime from ILicenseRegistry aligns with the PR's objective to clean up unused functionality. This change should simplify the interface and reduce the attack surface, provided that all dependencies and references to this function have been updated accordingly.

test/foundry/registries/LicenseRegistry.t.sol (1)

6-6: The updates in the test file correctly reflect the new structure and functionality introduced by LicenseRegistryHarness. However, ensure comprehensive test coverage for the new setExpirationTime method, especially focusing on edge cases and failure modes to ensure robustness.

Also applies to: 20-20, 266-392

Verification successful

The test coverage for the setExpirationTime method in LicenseRegistry.t.sol appears to be present, as indicated by the multiple instances of lrHarness.setExpirationTime found in the test file.

  • test/foundry/registries/LicenseRegistry.t.sol:
    • Lines containing lrHarness.setExpirationTime
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the comprehensive test coverage for `setExpirationTime`.

# Test: Search for test cases specifically targeting `setExpirationTime`.
rg --type solidity --files-with-matches 'test.*setExpirationTime' test/foundry/registries/

Length of output: 125



Script:

#!/bin/bash
# Description: Verify the comprehensive test coverage for `setExpirationTime`.

# Test: Search for test cases specifically targeting `setExpirationTime` in Solidity files.
rg 'setExpirationTime' test/foundry/registries/ --type-add 'solidity:*.sol'

Length of output: 660

test/foundry/utils/BaseTest.t.sol Show resolved Hide resolved
@Ramarti Ramarti merged commit 051a220 into storyprotocol:main Jun 27, 2024
3 checks passed
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.

3 participants