Widget: let the embed script load its display settings from our server
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 50/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- next.js, typescript
调研方向
Start by locating the embed script and the server-side widget/API routes; the payload does not name specific files or tests. Read the plan rules from merged issue #331 and the tracking issue #333, then trace how the script loads settings and how existing tests cover widget behavior. Done means the script safely falls back to defaults and the public lookup enforces server-side plan limits, caching, rate limits, and harmless handling of unknown or expired tokens, with tests and updated widget docs.
由索引模型根据 Issue 内容生成。
描述
The problem today
The small script businesses paste on their site knows nothing about the business. It can't learn that a business wants a different window size or bubble color, because it never asks our server anything.
What to build
A small public lookup the script calls when it loads. It tells the script how this business wants the widget to look.
- Returns display settings only (for example window size and bubble color). Never anything private.
- Cached so the page isn't slowed down, and rate limited.
- Which settings a business gets always follows their plan, decided on our server, never by what the install snippet says.
- Until a business has chosen anything, it returns today's defaults, so existing installs keep working without re-pasting the snippet.
Done when
- The script asks for its settings on load and falls back to today's look if the lookup fails or is slow
- The lookup is cached, rate limited, and returns only display settings
- An unknown or expired widget token gets a harmless default, not an error page
- Tests cover defaults, plan-based limits, caching headers and the rate limit
- The widget docs mention that display settings are read from the server
Depends on / related
- #331 (plan rules) is merged. This is the base for window sizes and brand color; see the tracking issue #333.
- 主要语言
- TypeScript
- 星标
- 16
- 派生
- 2
- 平均合并
- 6 小时 51 分钟
- 30 天内合并 PR
- 151
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
answerLoops/answerLoops 的其他 Issue
-
Widget: match the chat bubble color to the rest of the widget可能已有人在做 @uchiha-suraj 于 4 天前认领。 未关闭enhancement help wanted
难度 1/5 1-3 小时 新手友好度 84/100
answerLoops/answerLoops#345 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Widget: make the chat window fit on small phones可能已有人在做 @anushreemehta6 于 4 天前认领。 未关闭enhancement good first issue help wanted
难度 2/5 1-3 小时 新手友好度 82/100
answerLoops/answerLoops#344 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 85/100
answerLoops/answerLoops#17 ·
维护者通常 1 天内回复
-
documentation good first issue help wanted
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
enhancement good first issue help wanted
难度 4/5 3-5 天 新手友好度 34/100
answerLoops/answerLoops#372 ·
维护者通常 1 天内回复
查看 answerLoops/answerLoops 的全部 Issue
相似的 Issue
-
ai-driven-qa bug claude Minor
难度 2/5 1-3 小时 新手友好度 70/100
linagora/twake-contacts-frontend#241 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
ui(ListToolbar): search takes the full row on a phone instead of sharing it with the result count未关闭
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复
-
priority:high
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
ahmedkhaleel2004/gitdiagram#228 ·