Peace
Peace
good catch @glinda93 . Published 2.0.6 to address the key=0 bug. It sounds like there are different causes for the reported issue. Have you been able to debug it?
Sorry about that @aschmitz-wbd . Fix released in 2.0.7
The data passed to ModalSelector may contain anything you like. Taking the example from the Readme and modifying it: ``` const data = [ { key: index++, section: true, label:...
That should be ok. Please submit a PR and we'll merge right away.
Hopefully this doesn't cause unintended side effects. If it does, we could add a prop to control the onChange behavior -- previous work-around or none.
Try the prop `optionContainerStyle`. https://github.com/peacechen/react-native-modal-selector#props I'm not sure if that's what you're looking for. If not, a new prop may need to be added.
On second thought, you could use the wrapper mode and provide your own open button. See the `Wrapper` example: https://github.com/peacechen/react-native-modal-selector#usage
The `visible` prop controls whether the modal is displayed. Your component could set that value when pressed. https://github.com/peacechen/react-native-modal-selector#props
Please submit a PR, or try to find the line that adds the padding. I suspect it could be removed, or add a style prop to allow overriding it.
Good to hear that you found a solution. If any changes are required in RNMS, please submit a PR.