Skip to content

Add info about using classic destination with plugins #5700

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 3 commits into from
Nov 30, 2023

Conversation

ashton-huxtable
Copy link
Contributor

Proposed changes

Added a section about using classic/legacy destinations with destination plugins for new mobile libraries. Customers are frequently confused and will use the wrong destination.

Merge timing

  • ASAP once approved

Related issues (optional)

n/a

@ashton-huxtable ashton-huxtable marked this pull request as ready for review November 22, 2023 17:40
@ashton-huxtable ashton-huxtable requested a review from a team as a code owner November 22, 2023 17:40
@ashton-huxtable ashton-huxtable requested review from stayseesong and removed request for a team November 22, 2023 17:40
@stayseesong stayseesong merged commit 83ad413 into develop Nov 30, 2023
@stayseesong stayseesong deleted the ashton-huxtable-patch-2 branch November 30, 2023 20:52
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

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.

2 participants