Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat: support for large in-app messages #831
feat: support for large in-app messages #831
Changes from 1 commit
9c463fb
3984cbd
1611d2e
051799d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Not entirely sure about the impact here, but my assumption is that posting JSON might only work with this version of renderer and not the old one. And I believe it should still handle messages from both legacy editor and new editor without issues. However, just to be safe, can you please confirm if this change was intentional? It would also be helpful to mention this on linked ticket or in Slack so the squad is aligned and aware of the update.
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.
not sure i get it?
3.0
handles the new way of rendering and2.0
still handles the old way. So the folks who had older SDK version would keep on using 2.0 until they use 3.0?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.
This was exactly my question, whether
3.0
enforces any new requirements when composing in-app messages or if it's fully compatible with existing ones. From your response, it sounds like it is fully compatible. My only request here is to explicitly mention this update on ticket for reference, as I don't see it mentioned in ticket description or comments. I think calling this out clearly would be good for transparency.