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

4.x migration guide #106

Merged
merged 7 commits into from
Feb 1, 2024
Merged

4.x migration guide #106

merged 7 commits into from
Feb 1, 2024

Conversation

wzieba
Copy link
Collaborator

@wzieba wzieba commented Jan 19, 2024

Description

The new major release will introduce breaking changes to the SDK. This guide should make the transition smoother for SDK users.

How to test

Please see if this document makes sense to you, but it's not necessary to validate the content.

Copy link

codecov bot commented Jan 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ca04c4f) 70.54% compared to head (46d44e2) 70.54%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #106   +/-   ##
=======================================
  Coverage   70.54%   70.54%           
=======================================
  Files          21       21           
  Lines         404      404           
  Branches       49       49           
=======================================
  Hits          285      285           
  Misses        104      104           
  Partials       15       15           

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

@wzieba wzieba requested a review from iangmaia February 1, 2024 13:36
@wzieba wzieba marked this pull request as ready for review February 1, 2024 13:36
MIGRATION.md Outdated Show resolved Hide resolved
Co-authored-by: Ian Guedes Maia <[email protected]>
MIGRATION.md Outdated

---

For clarification on any of these changes or assistance with migrating your code to the latest version of the Parse.ly Android SDK, please contact our support team.
Copy link
Collaborator

@iangmaia iangmaia Feb 1, 2024

Choose a reason for hiding this comment

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

Totally optional, but mentioning just in case you like the idea / think it makes sense: because we're saying "please contact our support team", maybe we could add an email / link for that.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Good idea, thank you! I added a mail and suggested also opening a GitHub issue, which might be a shorter loop: 46d44e2

@wzieba wzieba merged commit 458644c into main Feb 1, 2024
3 checks passed
@wzieba wzieba deleted the 4.0-migration-guide branch February 1, 2024 14:37
@wzieba wzieba mentioned this pull request Feb 1, 2024
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