Respect macOS exclusions in the example autolinking workaround

Open
#337 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
react-native
Domain
mobile, tooling

Research direction

Start by reviewing the macOS autolinking workaround described in PR #298 and trace where it copies iOS configuration. Verify how explicit macOS null exclusions and known-compatible dependencies are represented, then check the resulting native dependency list. Done means incompatible iOS-only dependencies are not autolinked and explicit macOS exclusions remain intact.

Written by the indexing model from the issue text.

Description

PR #298 copies every dependency's iOS configuration to macOS when the macOS entry is null or missing. This can override an explicit macOS exclusion and autolink iOS-only native dependencies.

Limit the React Native macOS CLI workaround to known-compatible dependencies, preserve explicit null exclusions, and verify the resulting native dependency list.

Source: https://github.com/margelo/react-native-nitro-sqlite/pull/298

Dominant language
C
Stars
565
Forks
53
Avg merge
3d 13h
Merged PRs (30d)
28

Contributor guide

Open the contributing guide

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 margelo/react-native-nitro-sqlite

All issues in margelo/react-native-nitro-sqlite

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.