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: add setting a in-app event listener #147
feat: add setting a in-app event listener #147
Changes from 3 commits
6a1b435
6910c39
f34e991
075e3f0
70f6941
cbe8dd3
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.
Looks like we aren't using the receiver
Message
, so this should have been onInAppMessage
instead?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.
Sorry, I don't understand your question.
Is the question you have a question that Shahroz asked in this PR or a different question?
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.
I think what Rehan meant to say is, is an extension method on
build.gist.data.model.Message
and we aren't using the receiver "build.gist.data.model.Message" but we are using theInAppMessage
model only.So would it make more sense to have "InAppMessage" as a receiver rather than "build.gist.data.model.Message" which isn't being used.
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.
Shahroz got this right. I was suggesting this method to be following instead:
As I don't see
this
receiver used anywhere in the extension.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.
You already created
Message
extension earlier, do you think it would make more sense if we add it there?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.
I do enjoy extensions and see value in creating a
fun Message.getFromGistMessage(): InAppMessage
extension function.However, I do like encapsulating the construction of a
InAppMessage
object existing inside of theInAppMessage
object.If we want to leverage extensions, I vote we keep
InAppMessage.getFromGistMessage()
as-is but create an extension: