Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Flow's @platform attribute treated as part of the description

Open
#447 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
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
react-native
Domain
documentation, tooling

Research direction

Start by reproducing extraction from the React Native Button.js example, then trace how the Flow docblock is parsed. Done means the @platform android annotation is no longer included in the property's description and the extracted result matches the intended metadata behavior.

Written by the indexing model from the issue text.

Description

See: React Native Button.js

/**
   * TV next focus down (see documentation for the View component).
   *
   * @platform android
   */
  nextFocusDown?: ?number,

gets captured as:

"nextFocusDown": {
        "required": false,
        "flowType": {
          "name": "number",
          "nullable": true
        },
        "description": "TV next focus down (see documentation for the View component).\n\n@platform android"
Dominant language
TypeScript
Stars
3.8k
Forks
316
Avg merge
3h 28m
Merged PRs (30d)
6

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 reactjs/react-docgen

All issues in reactjs/react-docgen

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.