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

fix RCTAEPMessagingModule getLatestMessage and getCachedMessages #406

Closed
wants to merge 23 commits into from

Conversation

rymorale
Copy link
Contributor

@rymorale rymorale commented Dec 3, 2024

Description

Prevent exceptions from being thrown when casting a HashMap to ReadableMap. I noticed that there are some additional files that were added due to branching from @namArora3112's ios fix branch. If its easier to merge, I can just cherry pick my changes from faa352c.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@@ -84,7 +86,11 @@ public void getCachedMessages(final Promise promise) {

@ReactMethod
public void getLatestMessage(final Promise promise) {
promise.resolve(this.latestMessage);
if (this.latestMessage != null) {
promise.resolve(RCTAEPMessagingUtil.convertToReadableMap(convertMessageToMap(this.latestMessage)));
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's remove RCTAEPMessagingUtil. since we're using the "static import" for the method.

@cacheung
Copy link
Contributor

cacheung commented Dec 9, 2024

If we merge this PR to new_arch branch, do we need to also release messaging when it merge to main branch? Or we can have the messaging code update in main, but release to the npm later?
@yangyansong-adbe

Copy link
Collaborator

@namArora3112 namArora3112 left a comment

Choose a reason for hiding this comment

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

I have tested and it worked fine

@cacheung
Copy link
Contributor

cacheung commented Jan 6, 2025

I don't think we need to merge this PR to new_arc anymore. The changes are already in the main branch.

@namArora3112
Copy link
Collaborator

Already merged to the main branch

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.

4 participants