Skip to content

refactor!: remove the content-changed method from onSocketMessage #4679

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

Merged
merged 1 commit into from
Dec 12, 2022

Conversation

snitin315
Copy link
Member

@snitin315 snitin315 commented Dec 12, 2022

  • This is a bugfix
  • This is a feature
  • This is a code refactor
  • This is a test update
  • This is a docs update
  • This is a metadata update

For Bugs and Features; did you add new tests?

No.

Motivation / Use-Case

Remove the deprecated content-changed method.

Breaking Changes

BREAKING CHANGE: the content-changed method was removed in favor of the static-changed method.

Additional Info

No

@codecov
Copy link

codecov bot commented Dec 12, 2022

Codecov Report

Base: 92.28% // Head: 92.26% // Decreases project coverage by -0.01% ⚠️

Coverage data is based on head (addcbf5) compared to base (8996d36).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             next    #4679      +/-   ##
==========================================
- Coverage   92.28%   92.26%   -0.02%     
==========================================
  Files          15       15              
  Lines        1569     1565       -4     
  Branches      586      585       -1     
==========================================
- Hits         1448     1444       -4     
  Misses        112      112              
  Partials        9        9              
Impacted Files Coverage Δ
client-src/index.js 80.99% <ø> (-0.61%) ⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@snitin315 snitin315 marked this pull request as ready for review December 12, 2022 07:14
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.

2 participants