You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that the Turbo Android library can receive an option called pull_to_refresh_enabledvia the path configuration, which controls whether a view is refreshable.
I think it would be cool to have this feature in Turbo iOS too.
I wanted to check if you're cool with adding this feature to the library. If you like the idea, I'm happy to contribute and submit a pull request.
The text was updated successfully, but these errors were encountered:
I think that in the future we want to support all of those options available from Android! I'm working through presentation and context in my Turbo Navigator project. Which I'm hoping eventually will get merged upstream here.
Digging into this, adding any sort of Path Configuration reading might require a re-architecture of how turbo-ios works. Hence my other project which "wraps" this framework.
So I'm hesitant to merge a one-off PR that only handles one of these options and not all of them. At risk of having to rework the entire thing again in the near future.
But if you have an idea for a clean approach that doesn't change the public API then I'd love to see it! No promises on merging right now but it could kickstart a conversation.
Hi,
I've noticed that the Turbo Android library can receive an option called
pull_to_refresh_enabled
via the path configuration, which controls whether a view is refreshable.I think it would be cool to have this feature in Turbo iOS too.
I wanted to check if you're cool with adding this feature to the library. If you like the idea, I'm happy to contribute and submit a pull request.
The text was updated successfully, but these errors were encountered: