[New Rule] Expo Notifications

Open Beginner friendly
#1,468 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
android, kotlin
Domain
mobile

Research direction

Start with the listed Expo Notifications activity and service class names, then compare them with nearby library rules in the repository to follow its format. Add a rule identifying the listed classes and use the provided icon and description; done when the rule recognizes Expo Notifications in the listed apps.

Written by the indexing model from the issue text.

Description

Library filename / 库文件名

See Files & Comment

Library label / 库的文字标签

Expo Notifications

Library team / 库的开发团队

Expo

Files & Comment / 同组文件 & 备注
  • Activities:
expo.modules.notifications.service.NotificationForwarderActivity
  • Services:
expo.modules.notifications.service.ExpoFirebaseMessagingService
expo.modules.notifications.service.NotificationsService
In Apps / 出现于
Name Application ID VersionName VersionCode Source
BeastVault com.websloth.beastvault 1.1.3 75 Play Store
INTVL com.intvl.app 4.1.1 185 Play Store
LDLC com.groupeldlc.ldlcapp 2.3.0 2030001 Play Store
Steam com.valvesoftware.android.steam.community 3.10.11 10928360 Play Store
Library icon / 库图标

Expo Notifications icon from the Expo Repository: .github/resources/expo-notifications.svg

expo-notifications icon
Library description / 库描述

A library that provides an API to fetch push notification tokens and to present, schedule, receive and respond to notifications.

Library relative URL / 相关链接

https://github.com/expo/expo/tree/main/packages/expo-notifications

Dominant language
Python
Stars
201
Forks
85
Avg merge
1m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LibChecker/LibChecker-Rules

All issues in LibChecker/LibChecker-Rules

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.