Skip to content

Updating comment for syncPurchases#763

Merged
aboedo merged 3 commits into
mainfrom
Haley/update_syncPurchases_comment
Feb 6, 2023
Merged

Updating comment for syncPurchases#763
aboedo merged 3 commits into
mainfrom
Haley/update_syncPurchases_comment

Conversation

@HaleyRevcat

Copy link
Copy Markdown
Contributor

Updating comment for syncPurchases as there was some confusion with previous version stating that it could be called after each purchase.

Checklist

  • If applicable, unit tests
  • [ x ] If applicable, create follow-up issues for purchases-ios and hybrids

Motivation

Confusion with usage of syncPurchases, such as [here](https://community.revenuecat.com/sdks-51/when-should-i-call-syncpurchases-2502?postid=7942#post7942)

Description

Updated comment

Updating comment for syncPurchases as there was some confusion with previous version stating that it could be called after each purchase.
@HaleyRevcat

Copy link
Copy Markdown
Contributor Author

Should I update this in purchases-ios and hybrids as well? And how can I get the changes to propagate to the public sdk reference? https://sdk.revenuecat.com/android/5.0.0/purchases/com.revenuecat.purchases/-purchases/sync-purchases.html @aboedo @vegaro

@HaleyRevcat

Copy link
Copy Markdown
Contributor Author

Also not sure why the test failed, I don't think I did anything? 😣

@aboedo

aboedo commented Jan 30, 2023

Copy link
Copy Markdown
Member

@HaleyRevcat the test failed because of this:

Label the PR using one of the change type labels

We use labels to categorize changes in changelogs, like "new features", "bug fixes", etc.
I'll add a label to this one, docs and re-run the test

Updating in other repos would be great! I think iOS is okay, but I haven't checked the hybrids.

@aboedo aboedo self-assigned this Jan 30, 2023
@aboedo aboedo added the docs label Jan 30, 2023
Comment on lines +216 to +217
* for subscriptions anytime a sync is needed, like after a successful purchase, or when migrating existing
* users to RevenueCat
* for subscriptions anytime a sync is needed, such as when migrating existing users to RevenueCat
*

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

image

Not sure what's going on with the thing it's complaining about from line 1, but it's safe to ignore since it wasn't modified in this PR.
The other one, however, is from this PR, and it's complaining about this extra line (217), since we'd have two consecutive lines that have nothing in it.
Could you remove line 217?

@HaleyRevcat

Copy link
Copy Markdown
Contributor Author

@aboedo I got rid of line 217, can this be merged?

@codecov

codecov Bot commented Feb 2, 2023

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.54%. Comparing base (f091f6b) to head (dbbc812).
Report is 941 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #763   +/-   ##
=======================================
  Coverage   81.54%   81.54%           
=======================================
  Files         121      121           
  Lines        3999     3999           
  Branches      512      512           
=======================================
  Hits         3261     3261           
  Misses        535      535           
  Partials      203      203           

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

@aboedo

aboedo commented Feb 6, 2023

Copy link
Copy Markdown
Member

yes! marking as ready for review and merging

@aboedo aboedo marked this pull request as ready for review February 6, 2023 20:23
@aboedo aboedo merged commit ed350ff into main Feb 6, 2023
@aboedo aboedo deleted the Haley/update_syncPurchases_comment branch February 6, 2023 21:47
@vegaro vegaro added pr:other and removed pr:docs labels Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants