[New Rule] Expo Clipboard

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

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
76/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile-dev

Research direction

The issue identifies the library as Expo Clipboard and names expo.modules.clipboard.ClipboardFileProvider as a content provider. Start by reading the repository’s existing library rules and check how provider class names, the icon, and the package link are represented. Add a rule for Expo Clipboard using the details in the issue; done when it matches the repository’s rule format and identifies the library correctly.

Written by the indexing model from the issue text.

Description

Library filename / 库文件名

See Files & Comment

Library label / 库的文字标签

Expo Clipboard

Library team / 库的开发团队

Expo

Files & Comment / 同组文件 & 备注
  • Content providers:
expo.modules.clipboard.ClipboardFileProvider
In Apps / 出现于
Name Application ID VersionName VersionCode Source
BeastVault com.websloth.beastvault 1.1.3 75 Play Store
Doctolib fr.doctolib.www 5.17.0 322453 Play Store
INTVL com.intvl.app 4.1.1 185 Play Store
Library icon / 库图标

Expo Clipboard icon from the Expo Repository: .github/resources/expo-clipboard.svg

expo-clipboard icon
Library description / 库描述

A universal library that allows getting and setting Clipboard content.

Library relative URL / 相关链接

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

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.