leecade / leecade/react-native-swiper
React-native-swiper overlaying images from sides, Looks dirty
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.5k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
I am using react-native-swiper library in react-native-snap-carousel, but native-swiper showing me overlaying image from side, and looks so bad, i have tried, but unable to do.
see screenshot:
Here is the code:
SliderEntry.js
render() {
return (
<View style={styles.slideInnerContainer} >
<View>
<Swiper
width={300}
showsButtons
>
<View>
<Image
source={{ uri:
'http://primecourierservices.co.uk/wp-
content/uploads/2018/11/van-courier-
service-london-uk.jpg' }}
style={{width: 330, height: 250
}}
/>
</View>
<View>
<Image
source={{ uri:
'http://primecourierservices.co.uk/wp-
content/uploads/2018/11/van-courier-
service-london-uk.jpg' }}
style={{width: 330, height: 250
}}
/>
</View>
<View>
<Image
source={{ uri:
'http://primecourierservices.co.uk/wp-
content/uploads/2018/11/van-courier-
service-london-uk.jpg' }}
style={{width: 330, height: 250
}}
/>
</View>
</Swiper>
</View>
<View>
<Text style={{marginBottom: 10}}>{uppercaseTitle}</Text>
<View style={{marginLeft: 19, marginTop: 5, marginBottom: 6}}>
<Text>
{van}
</Text>
</View>
</View>
</View>
);
}
Can anyone help me with this? Please
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the SliderEntry.js example and compare the Swiper width of 300 with the Image width of 330. Reproduce the supplied screenshot, then verify that the resulting carousel no longer shows adjacent images overlaying from the sides.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100