Working with gestures
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- fsharp, react-native
- Domain
- mobile
Research direction
Start at src/Fable.Helpers.ReactNative.fs around IViewProperties and its IGestureResponderHandlers inheritance, then inspect the PanResponderCallbacks and panResponder.panHandlers usage shown in the issue. Confirm how React Native gesture handlers are represented in the F# bindings and document a working way to pass them to a view, including the equivalent of JavaScript's spread behavior.
Written by the indexing model from the issue text.
Description
Hey there, I'm trying to work with some animation stuff and I'm having some difficulties. You may have seen my PR alread but I do have another issue that I'd like to understand how to fix it.
The interface IViewProperties inherits from IGestureResponderHandlers
And I was wondering how I could pass it to the view.
I began creating an object:
let panResponderConfig = createEmpty<Fable.Import.ReactNative.PanResponderCallbacks>
let panResponder = RN.PanResponder.create(panResponderConfig)
But then, how am I suppose to pass panResponder.panHandlers to the view?
Usually with javascript this is done this way:
this._panResponder = PanResponder.create({ .... })
<View {...this._panResponder.panHandlers}>....</View>
How can I replicate JavaScript's spread operator and how can I pass that to IViewProperties?
Thanks
- Dominant language
- F#
- Stars
- 53
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from fable-compiler/fable-react-native
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
fable-compiler/fable-react-native#65 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
fable-compiler/fable-react-native#60 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
fable-compiler/fable-react-native#59 · 8 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
fable-compiler/fable-react-native#54 · 7 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
fable-compiler/fable-react-native#53 · 1 comment ·
All issues in fable-compiler/fable-react-native
Similar issues
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
clerk/javascript#10033 ·
Maintainers usually reply within 1 day
-
React-Native Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-react-native#6822 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
ooni/probe-multiplatform#1614 · 1 comment ·
Maintainers usually reply within 1 day