Skip to content

Document _ prefixed props (eg: _ItemSeparatorComponent) or change this #5

@MoOx

Description

@MoOx
Member

Coming from JS, this can be disturbing. You could think it's unused, since _ are often unused to avoid non usage warning.

We could also try to remove them & use lowercase.

Thoughts @cknitt @sgny ?

Activity

cknitt

cknitt commented on Aug 20, 2019

@cknitt
Member

AFAIK the _ props are the only way this works with @bs.obj and thereby @react.component - @bs.as is not supported here.

sgny

sgny commented on Aug 20, 2019

@sgny

It appears we responded at the same time.

This is already addressed in BuckleScript documentation however, we might as well add a reference to that. The leading _ is ignored when an uppercase letter follows and I understand some of these props are supposed to begin with an uppercase letter. I don't understand the design decision that makes these props so particularly special that they could not have been in lowercase, but that's a different kettle of fish.

To be honest, coming from JavaScript nothing should be too weird 😁.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @MoOx@cknitt@sgny

        Issue actions

          Document `_` prefixed props (eg: _ItemSeparatorComponent) or change this · Issue #5 · rescript-react-native/rescript-react-native.github.io