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

refactor: update emoji.json now includes hex, dec and unicode along with removal of AbstractEmoji and expose IEmoji #224

Merged
merged 2 commits into from
May 23, 2024

Conversation

wax911
Copy link
Member

@wax911 wax911 commented May 23, 2024

AniTrend Pull Request

Thank you for contributing! Please take a moment to review our contributing guidelines to make the process easy and effective for everyone involved.

Please open an issue before embarking on any significant pull request, especially those that add a new library or change existing tests, otherwise you risk spending a lot of time working on something that might not end up being merged into the project.

Before opening a pull request, please ensure you've done the following:

  • You have followed our contributing guidelines
  • Double checked that your branch is based on develop and targets develop (where applicable)
  • Pull request has tests (if applicable)
  • Documentation is updated (if necessary)
  • Description explains the issue/use-case resolved

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Enhancement (Improves existing functionality)

IMPORTANT: By submitting a patch, you agree to allow the project owners to license your work under the terms of the Apache License 2.0.

- Removes `AbstractEmoji` and exposes `IEmoji`
@wax911
Copy link
Member Author

wax911 commented May 23, 2024

@yoobi ready for review ⚡

@yoobi
Copy link
Contributor

yoobi commented May 23, 2024

Neat PR, nothing more to add, really cool we don't need AbstractEmoji anymore :)

@yoobi
Copy link
Contributor

yoobi commented May 23, 2024

Maybe I could commit on this branch to add consumer-rules.pro as to have a single release

@yoobi
Copy link
Contributor

yoobi commented May 23, 2024

Oh we have committed at the same time, I'll close my PR, yours is better

@wax911
Copy link
Member Author

wax911 commented May 23, 2024

Oh we have committed at the same time, I'll close my PR, yours is better

Haha, whoops. I figured we might as well, I assumed you were busy so went ahead and added some. I don't think they're perfect and may need some fine tuning though. So fee free to suggest 😉

@yoobi
Copy link
Contributor

yoobi commented May 23, 2024

I've had the same rules even less than what you did and it worked when I tried for all 3 serializers

@wax911
Copy link
Member Author

wax911 commented May 23, 2024

I've had the same rules even less than what you did and it worked when I tried for all 3 serializers

Great to hear, I'll merge this in. We can test the commit hash as our version and create a new release if you're happy with the outcome 😃

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Auto approved automated PR

@wax911 wax911 merged commit 8e6c35a into develop May 23, 2024
11 checks passed
@wax911 wax911 deleted the refactor/computed-hex-and-dec-for-emoji-json branch May 23, 2024 20:21
@wax911 wax911 linked an issue May 23, 2024 that may be closed by this pull request
@yoobi
Copy link
Contributor

yoobi commented May 28, 2024

I've tried checking 92bccf057a but I get Failed to resolve: com.github.anitrend.android-emojify:moshi:92bccf057a

@wax911
Copy link
Member Author

wax911 commented May 29, 2024

@yoobi not sure what the commit hash you're using points to but the latest commit hash on develop is e0369c5 so you should be using https://jitpack.io/#anitrend/android-emojify/e0369c5fae -> implementation 'com.github.anitrend.android-emojify:{module_here}:e0369c5fae'

@yoobi
Copy link
Contributor

yoobi commented May 29, 2024

Oh right, I was looking at jitpack builds and the last one was pointing at 92bccf057a
I've tested the last version e0369c5fae and it seems to be working in my project with release mode

@wax911
Copy link
Member Author

wax911 commented May 29, 2024

I'll hold off publishing the tag till Friday in case you uncover any issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue in release mode
2 participants