droidconKE / droidconKE2022ReactNative

Official DroidconKE 2022 React Native App
https://play.google.com/store/apps/details?id=com.brianwachira.droidconKE2022ReactNative&hl=en&gl=US
MIT License
8 stars 17 forks source link

[UI] Create Feeds Screen #8

Closed brianwachira closed 1 year ago

brianwachira commented 2 years ago

Create Feed Screen as per the guideline - Feed Screen Design Adobe XD Link

Follow contribution guidelines laid out in our contribution guide

Screenshot 2022-09-12 at 21 14 34

mog-rn commented 1 year ago

@brianwachira I can work on this before the session's screen is done

brianwachira commented 1 year ago

@brianwachira I can work on this before the session's screen is done

If you are still up for this then go ahead! Feel free to assign yourself this issue. All the best!

orama254 commented 1 year ago

Hello @Mogakamo ,

how is the progress for this issue?

any blockers that you may have encountered and would like assistance with?

mog-rn commented 1 year ago

@orama254 Hello, I am doing well. I have been having issues getting to install the packages after I updated my local repo. I have also talked with @brianwachira but I don't know what is causing the issue. However, I will be able to make an update on my progress before the end of tomorrow incase I am not able to solve the issue

brianwachira commented 1 year ago

@orama254 Hello, I am doing well. I have been having issues getting to install the packages after I updated my local repo. I have also talked with @brianwachira but I don't know what is causing the issue. However, I will be able to make an update on my progress before the end of tomorrow incase I am not able to solve the issue

@Mogakamo please share the issue you are getting on installing packages over here

mog-rn commented 1 year ago

`> droidconke2022reactnative@1.0.0 start C:\Users\Mogaka.dev\Desktop\droidconKE2022ReactNative

expo start

internal/modules/cjs/loader.js:1088 throw err; ^

Error: Cannot find module 'shebang-command' Require stack:

mog-rn commented 1 year ago

@brianwachira @makunomark it's all clear the npm version that I was using was the one that was causing the errors. I am currently working on it now