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

backport im services - 4.3 #6402

Merged
merged 1 commit into from
Mar 31, 2020
Merged

backport im services - 4.3 #6402

merged 1 commit into from
Mar 31, 2020

Conversation

lazedo
Copy link
Member

@lazedo lazedo commented Mar 23, 2020

  • compatibility with master

@lazedo lazedo force-pushed the kapi_im branch 3 times, most recently from efd47b0 to b5b2feb Compare March 23, 2020 18:15
@lazedo lazedo changed the title backport im services backport im services - 4.3 Mar 25, 2020
@lazedo lazedo marked this pull request as ready for review March 27, 2020 23:44
Copy link
Member

@jamesaimonetti jamesaimonetti left a comment

Choose a reason for hiding this comment

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

Added a commit with dialyzer updates; just one outstanding question

Map#{fetch_id => kapps_im:message_id(IM)
,message_id => kapps_im:message_id(IM)
,im => IM
};
create_im(Map) -> Map.

-spec maybe_update_sender(kapps_im:im()) -> kapps_im:im().
maybe_update_sender(Im) ->
case kapps_im:endpoint(Im) of
Copy link
Member

Choose a reason for hiding this comment

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

Dialyzer doesn't think undefined will be reached, since the Im record defaults to empty JSON object. Would you prefer to test for empty JObj and return Im unmodified or just bind EP and update the From?

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