Real world adoption challenges
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 20/100
- Issue 類型
- 文件
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- javascript, react-native
研究方向
未識別出檔案或測試。首先檢查範例的函式 App 元件、StreamApp 的巢狀結構、token 取得流程以及 react-native-navigation 設定；完成標準應是一項範圍明確的變更，或一份說明所支援之驗證與導覽整合的文件。
由索引模型根據 Issue 內容生成。
描述
Before I begin, I was pleased with this example. It's one of the better examples I think that has been done.
First of all I know this example probably was not intended or conceived to be a real world example (it loads dummy data) but please humor me as I struggle to adopt it as such.
-
This example uses a functional component as the App. If I'm wrong please let me know. Thereby from my understanding this means that it cannot have state. To set the stage for why I find adoption challenging, the STREAM_API_TOKEN is a user token generated by the backend and handed to the mobile app per: https://getstream.io/react-native-activity-feed/tutorial/. Naturally this value must either be held already in mobile async storage or better be passed back by an API call asynchronously. Yet we just said this example has a stateless nature. I also referred to: https://getstream.github.io/react-native-activity-feed/#introduction in terms of how the StreamApp component must have the feeds nested. Most of my issues have circled around this as I kept trying to figure out how to pass and construct the components together. Surely we shouldn't pass the STREAM_API_TOKEN by props? Right now my stream client in python is returning the user token by my API.
-
It appears if #1 does work in the real world this example suggests that because the feeds are elements of this "parent" component, the navigation must also derive from the parent component. Currently, I'm using react-native-navigation via method call (not expo or anything else) and so this would require that I probably rewrite how my navigation is built. Any suggestions on what my options are within how the react native activity feed must be designed?
-
I certainly faced the issue in this SO question: https://stackoverflow.com/questions/52110253/you-are-publicly-sharing-your-app-secret-do-not-expose-the-app-secret-in-browse. I sort of understand the answer provided, but also do not because at least in a mobile app (not a server client) I would think you would get the user generated token passed back by API. Am I thinking about the generation of the user token entirely wrong? Should generation be done in a function inside the functional component described in question 1? Could that solve my woes about obtaining the token to some extent? I'm not sure because I still feel I would need some level of stateful / asynchronous interaction for authentication via my API.
Thank you for sharing any advice you may have for easier adoption. Cheers!
- 主要語言
- JavaScript
- 星號
- 340
- 分支
- 193
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
GetStream/react-native-example 的其他 Issue
-
難度 4/5 3-5 天 新手友好度 35/100
GetStream/react-native-example#52 · 9 則留言 · 4 個 reaction ·
-
難度 4/5 3-5 天 新手友好度 18/100
GetStream/react-native-example#45 · 1 則留言 ·
-
難度 5/5 一週以上 新手友好度 20/100
GetStream/react-native-example#39 · 2 則留言 ·
-
Error when trying to run expo example可能重新可做 @vishalnarkhede 於 2008 天前認領，目前沒有進行中的 PR。 未關閉
GetStream/react-native-example#38 · 11 則留言 · 10 個 reaction · 已指派 1 人 ·
-
難度 3/5 1-2 天 新手友好度 25/100
GetStream/react-native-example#35 · 1 則留言 ·
查看 GetStream/react-native-example 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 4 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
-
[quality] useFocusTrap's Shift+Tab wrap and non-Tab/non-Escape key arms are never driven end to end可能已有人在做 @hivecommons-hive 今天認領。 未關閉agent/quality hive/covered-by-pr hive/hosted-available-lke648397-260827-5n31 quality testing
難度 2/5 1-3 小時 新手友好度 85/100
維護者通常 1 天內回覆
-
agentic-workflows
難度 1/5 1 小時以內 新手友好度 85/100
githubnext/gh-aw-workshop#4220 ·
維護者通常 1 天內回覆