How hsinghal153/rnfuncsetup works
This is a React Native starter app: its visible user workflow launches the registered component and displays the stock instructional screen. The repository also contains Redux login-request plumbing, but the sampled App does not connect to that store, so it is shown as a separate capability rather than part of the screen flow. Login source is sampled; the root saga and API URL definitions are not, so their internal wiring is omitted.
Main entry points: store.tsx Redux store · login.saga.js Login saga · HTTPRequest.tsx HTTP requests · APIKit.tsx API client
Components 15
App screen
- JS registration
index.js - Starter screen
App.tsx
State and login
- Redux store
src/Redux/store.tsx - User request state
src/Redux/Slice/userSlice.js - Token state
src/Redux/Slice/getToken.js - Root saga
src/Redux/rootSaga.tsx - Login saga
src/Redux/Middleware/SagaApi/login.saga.js - HTTP requests
src/Util/HTTPRequest.tsx - API client
src/Util/APIKit.tsx - API endpoints
src/Util/Api_Url.tsx - Error messages
src/Util/AppUtils.tsx
Native launch
- Android activity
android/app/src/main/java/com/awesomepr/MainActivity.kt - iOS delegate
ios/AwesomePr/AppDelegate.swift
Other components
- App user
- Remote API
Connections 15
- App user → Android activity: launches
- App user → iOS delegate: launches
- Android activity → JS registration: registers component
- iOS delegate → JS registration: loads bundle
- JS registration → Starter screen: renders
- Redux store → Root saga: runs
- Redux store → User request state: reduces state
- Redux store → Token state: reduces state
- User request state → Login saga: request triggers
- Login saga → HTTP requests: calls login
- Login saga → Token state: updates user state
- HTTP requests → API client: posts request
- HTTP requests → API endpoints: uses endpoint
- API client → Remote API: sends request
- API client → Error messages: shows errors