Nativebase: This is why my client says react native sucks
Hi! Thanks for huge work for NativeBase!
I understand how hard it is to develop and maintain this framework, but there are some glitches i can not pass by.
I just run yarn run ios on freshly downloaded master branch and opened Header/Icon and Text Buttons.
Did you see how title text aligned in the "back" button? And what is the strange padding size for the right bar button?
I trying to return to react native + Nativebase every 2-3 month, but every time i faces some glitches like this which stops me to use this technology, beside it offer cross platform development.
The questions for RN developers:
- do you really fix every small similar issue like this by the hand?
- do you really fix every small similar issue like this or you just does not recognise them?
- does your users really enjoy using your applications with such UI full of cracks?
roma86
All 5 comments
I must say I'm a bit disappointed myself with the issues with this framework. This issue has already been reported and closed without being fixed, see #1724 . I stopped caring about this issue because I struggled to get #1731 fixed which was not easy. It took three releases to get #1731 fixed. Even though I provided a concrete example of the bug and a hint of what may be wrong the fix was not tested before closing the issue. I really struggled to convince the issue was still there with examples but my examples was never used for testing the fix.
I understand that this is a community project so I cannot expect too much but still this have been a bit too much. One thing that really bothers me though is this project has at the moment 8726 github stars and still almost no other people backed me up on these issues in the core functionality of this framework. And since the development team did not care too much about them I almost felt I was reporting issues caused by incorrect usage.
andidev
on 11 May 2018
@roma86 @andidev Along with attending and fixing issues, we are revising all of the NativeBase components
Hence expect a day's time to fix this
SupriyaKalghatgi
on 14 May 2018
Check fix/header for fix
SupriyaKalghatgi
on 16 May 2018
@roma86 @andidev Fixed with 2.4.5
Check NativeBase-KitchenSink for updated code
Check NativeBase Docs Header
SupriyaKalghatgi
on 18 May 2018
SupriyaKalghatgi
on 21 May 2018
Related issues
kitsune7
路
3Comments
sihemhssine
路
3Comments
muthuraman007
路
3Comments
chetnadaffodil
路
3Comments
maphongba008
路
3Comments
Most helpful comment
I must say I'm a bit disappointed myself with the issues with this framework. This issue has already been reported and closed without being fixed, see #1724 . I stopped caring about this issue because I struggled to get #1731 fixed which was not easy. It took three releases to get #1731 fixed. Even though I provided a concrete example of the bug and a hint of what may be wrong the fix was not tested before closing the issue. I really struggled to convince the issue was still there with examples but my examples was never used for testing the fix.
I understand that this is a community project so I cannot expect too much but still this have been a bit too much. One thing that really bothers me though is this project has at the moment 8726 github stars and still almost no other people backed me up on these issues in the core functionality of this framework. And since the development team did not care too much about them I almost felt I was reporting issues caused by incorrect usage.