flexsurfer / rn-shadow-steroid

React Native with shadow-cljs on steroids

/_/\
( o.o )

^ <

rn-shadow-steroid's Issues

Picker component deprecation

When running the react-native application with the latest react-native version I get the deprecation warning that the Picker is now deprecated in react-native, and will be removed in the next release.

Instead, one should switch to the @react-native-community/picker component.

More info at the new picker project page

The picker component should either be removed from the steroid.rn.core namespace or kept there, but use the new implementation instead.

Add wrappers for additional react-native libraries

As discussed in #2 and #3 please add wrappers for the following common components. Ideally they should reside in separate namespace, and don't influence the build if not required.

• https://github.com/react-native-community/async-storage
• https://github.com/react-native-community/react-native-picker - mentioned in #3
• https://github.com/react-native-community/datetimepicker
• https://github.com/oblador/react-native-vector-icons - with support for various icon sets

extract navigation into separate project?

rn-shadow-steroid works great for its primary purpose of seamlessly wrapping react-native components and providing a support for hot-reloading while developing using shadow-cljs. The base is simple and works great with the pure reagent. I can see it as a dependency for every Clojurescript react-native project.

However, the react-navigation support adds additional functionality on top of that, and pulls additional dependencies, like re-frame. This makes the project more opinionated regarding the tech stack, and this part can as well justify itself to be a separate library.

Are there any plans to split this project into the small core, and separate project for navigation, or it's going to be kept as is?

Or, in case of "all in one" approach, are there some plans to add more wrappers for react native components, for example for native-base or react-native-elements?

Question: why are basic react-native components split between many different namespaces?

Why are components imported from the original "react-native" package split between multiple Clojurescript packages?

It's just me, but I found the old way where you only needed to import steroid.rn.core and have all basic react-native ui components right there instead of requiring multiple packages.

fix flatlist

(reagent/as-element (f (.-item data) (.-index data) (.-separators data))

Version 0.2.9 Release

Hello!

With the recent update to use @react-native-picker/picker and @react-native-masked-view/masked-view instead of their @react-native-community/* counterparts, when will a 0.2.9 release be deployed?

I am currently stuck on an older react 16 version, and in attempting to upgrade, the community versions of those packages cause a peer dependency conflict.

Thanks for the work on this project, by the way!

Add wrapper for react-native-vector-icons

original issue #4

As discussed in #2 and #3 please add wrappers for the following common components. Ideally they should reside in a separate namespace, and don't influence the build if not required.

https://github.com/oblador/react-native-vector-icons - with support for various icon sets

PR is welcomed: https://github.com/flexsurfer/rn-shadow-steroid/blob/master/src/steroid/rn/components/vector_icons.cljs#L3

Use :reload-strategy :full

In latest version of shadow-cljs you now have the :reload-strategy :full in :devetools which should simplify your hot-reloading