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

chore(contracts): Frequent Use of memory Parameters Where calldata Would Be Possible #898

Conversation

alainncls
Copy link
Collaborator

What does this PR do?

Related ticket

Fixes #897

Type of change

  • Chore
  • Bug fix
  • New feature
  • Documentation update

Check list

  • Unit tests for any smart contract change
  • Contracts and functions are documented

@alainncls alainncls self-assigned this Jan 31, 2025
@codecov-commenter
Copy link

codecov-commenter commented Jan 31, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.74%. Comparing base (7c15db0) to head (2976cce).
Report is 1 commits behind head on dev.

Additional details and impacted files
@@             Coverage Diff             @@
##              dev     #898       +/-   ##
===========================================
+ Coverage   48.59%   75.74%   +27.15%     
===========================================
  Files          18       40       +22     
  Lines         391      936      +545     
  Branches       63      165      +102     
===========================================
+ Hits          190      709      +519     
- Misses        198      224       +26     
  Partials        3        3               

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@alainncls alainncls force-pushed the chore/frequent-use-of-memory-parameters-where-calldata-would-be-possible branch from 4a14c21 to 2976cce Compare February 4, 2025 10:34
@alainncls alainncls merged commit e2e7f11 into dev Feb 4, 2025
10 checks passed
@alainncls alainncls deleted the chore/frequent-use-of-memory-parameters-where-calldata-would-be-possible branch February 4, 2025 10:41
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.

[TASK] Frequent Use of memory Parameters Where calldata Would Be Possible
3 participants