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

feat(ref-range): support default range change util #1351

Merged
merged 1 commit into from Feb 7, 2024

Conversation

Gggpound
Copy link
Contributor

@Gggpound Gggpound commented Feb 7, 2024

  • I am sure that the code is update-to-date with the dev branch.

close #

Copy link

github-actions bot commented Feb 7, 2024

View Deployment

#7809351526

🥐 🍔 🥓 🥗 🥘 🌯 🍚 🍛 🍖 🍭 🍧 🍝 🥪 🥖 🍪
Still cooking, please come back later
🥙 🥮 🥨 🌭 🍦 🍙 🍕 🍰 🍮 🍜 🍡 🍱 🍿 🍕 🥟

Copy link

codecov bot commented Feb 7, 2024

Codecov Report

Attention: 37 lines in your changes are missing coverage. Please review.

Comparison is base (bd57a84) 29.72% compared to head (ee9113d) 29.70%.
Report is 1 commits behind head on dev.

Files Patch % Lines
packages/sheets/src/services/ref-range/util.ts 2.63% 37 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #1351      +/-   ##
==========================================
- Coverage   29.72%   29.70%   -0.03%     
==========================================
  Files         844      844              
  Lines       47874    47912      +38     
  Branches     9813     9824      +11     
==========================================
+ Hits        14231    14232       +1     
- Misses      33643    33680      +37     

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

@Gggpound Gggpound merged commit 54512ea into dev Feb 7, 2024
7 checks passed
@Gggpound Gggpound deleted the feat-ref-range-0207 branch February 7, 2024 06:42
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.

None yet

2 participants