List Component

[tolu360]

Hello,

Please, this is more of a question: Is work still on-going on the List component? I noticed it was commented out in the demo app and it threw errors when I tried to uncomment and run the app with it.

And please is it normal native behaviour for the drawer to be available on every view, even child views? It feels like an anti-pattern, what do you think? Thanks

[Ehesp]

Hello, yeah it'll be in the next release, see the 0.4 roadmap.

You're not the first person to comment about the drawer. It's an easy fix though, in the demo app routes.js file, the other pages would just be nested as a child of the welcome route. I'm not so sure on how it should behave here to be honest, since those other pages are technically parents and unrelated to welcome.... hm.

(Also sorry about the closing/reopening, was on my phone).

[tolu360]

Thanks for the quick reply @Ehesp. Not quite sure how the drawer 'should' behave myself - I think it's not so opinionated, even there are disparities in its behaviour across apps by Google e.g GMail follows your pattern (drawer is available globally) but on Hangouts (drawer is not available in child views). On most apps though, the back button would only exit app when you are on the landing or initial view.

[Ehesp]

Also with the List view, I need some way of having a global wrapper for TouchableNativeFeedBack and also Ripple, instead of doing the whole if(!isCompatible... scenario every time. Will sort that somehow.

Yeah, there's all sorts of inconsistency with Google really, some of the apps "sort of" follow Material Design too, which is annoying.

The demo app uses the Navigate class, which by default only quits the app if you're on a top level parent. It wouldn't be too much hassle to customise it for your needs - every app is different, just hard to make a fits all solution.

[tolu360]

Thank you and you are right, your library can be easily customised.