Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

problem with selected

See original GitHub issue

Hi guys,

Having a small issue working with the plugin

<Select
  selected='MALE'
>
  <Option value='FEMALE'>female</Option>
  <Option value='MALE'>male</Option>
  <Option value='UNKNOWN'>other</Option>
</Select>

this is not selecting by default the male. Any thoughts?

Issue Analytics

State:
Created 6 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

gs-akhancommented, Sep 5, 2017

Yes, So the SELECT component actually need not know what is selected inside it. The outer your component can hold the state of selected value.

The defaultText makes it appears to user that the values is selected.

On Tue, Sep 5, 2017 at 11:51 PM, Panagiotis Vourtsis < notifications@github.com> wrote:

ah sorry. i mean that with the defaultText i cannot decide based on the value can i? I can only show a “dummy” text

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/gs-akhan/react-native-chooser/issues/35#issuecomment-327260577, or mute the thread https://github.com/notifications/unsubscribe-auth/AFYnVn3g87CoOGI_v8YL-V0b8gCaDIByks5sfZEjgaJpZM4PNBoP .

0reactions

gs-akhancommented, Sep 6, 2017

Super. That will work.

I just wanted to keep selectedText as only property. other authors made PRs and they added new properties and it made it ambiguous… 😦

However whatever you did should work. Again the <Select /> component doesn’t hold any state. you set values from outside and get callback executed when you change.