-
Notifications
You must be signed in to change notification settings - Fork 380
Not all destinations support arrays as properties #1721
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
Conversation
Add note for each event that shows an array as a property, to tell users that not all destinations accept arrays as properties. Request from CSM, to clear up common customer confusion, here: https://segment.slack.com/archives/CALA7QMJQ/p1623769073212700
✔️ Deploy Preview for segment-docs ready! 🔨 Explore the source changes: e2480b9 🔍 Inspect the deploy log: https://app.netlify.com/sites/segment-docs/deploys/60e4a56bf6844500077d22ff 😎 Browse the preview: https://deploy-preview-1721--segment-docs.netlify.app |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added some format changes to the notes
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Add note for each event that shows an array as a property, to tell users that not all destinations accept arrays as properties. Request from CSM, to clear up common customer confusion, here: https://segment.slack.com/archives/CALA7QMJQ/p1623769073212700
Merge timing