ARTICLE DETAIL

资讯详情

深耕网站视觉设计与运营推广的一线实战洞察。

[特殊字符] IMPORTANT

[特殊字符] IMPORTANT IMPORTANT【免费下载链接】posthog:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.项目地址: https://gitcode.com/GitHub_Trending/po/posthogThis issue is likely user-facing in the main PostHog app, seesurveyVersionRequirements.ts. If you delete or close this issue, be sure to update the version requirements list here.SummaryThe [SDK] SDK does not support [feature] for surveys.Current State[What exists, if anything - types, partial implementation, etc.]Expected Behavior[What should happen when this feature is configured]Reference ImplementationSee posthog-js browser:packages/browser/src/extensions/surveys.tsFor mobile-specific patterns, see posthog-react-native:packages/react-native/src/surveys/getActiveMatchingSurveys.tsRelated[links to the sibling SDK issues created for the same feature — list the ones that exist at creation time; the rest are backfilled below]This issue was generated by Claude using the/survey-sdk-auditskill.模板中的 ## Related 段承担跨仓库 Issue 的横向关联——这也呼应了技能开篇所述“Survey SDK feature parity 没有集中跟踪 Issue可见性由 surveyVersionRequirements.ts 链接各不支持 SDK 的 Issue 每个新 Issue 通过 ## Related 互链”的机制设计。 ### 8.5 回填兄弟 Issue 链接Backfill Issue 逐个创建先建的 Issue 无法链接尚不存在的兄弟 Issue。全部创建完成后需回填 **Step 1**拉取当前正文到临时文件 bash gh issue view 123 --repo PostHog/posthog-ios --json body --jq .body /tmp/issue_body.mdStep 2在临时文件中填入兄弟 Issue 链接并移除占位符让用户在推送前审阅 diff。Step 3推送更新gh issue edit 123 --repo PostHog/posthog-ios --body-file /tmp/issue_body.md九、完成清单Completion Checklist结束审计前逐项核对理解特性— 阅读surveyVersionRequirements.ts中的 check 函数检查浏览器 SDK— 在变更日志中找到版本这是参考实现检查 react-native SDK— 在变更日志中找到版本检查 iOS SDK— 验证功能确实实现而非仅类型检查 Android SDK— 验证功能确实实现而非仅类型检查 Flutter SDK— 核对原生依赖版本搜索存量 Issue— 创建新 Issue 之前创建 GitHub Issues— 为所有不支持 SDK 创建使用正确标签更新 surveyVersionRequirements.ts— 修正版本号、为unsupportedSdks补充 issue 链接重新生成 SDK 对齐文档— 运行pnpm --filterposthog/frontend build:survey-sdk-docs更新 sdk-feature-support.mdx回填兄弟链接— 全部 Issue 创建后更新每个 Issue 的 Related 段使所有兄弟 Issue 互链十、常见陷阱Common Pitfalls不要猜版本— 始终用变更日志或 Git 历史验证类型 ≠ 实现— 数据类有字段不代表过滤逻辑存在模型字段 ≠ 功能支持— 字段可能被解析但从未参与决策如linkedFlagKey存在但缺linkedFlagVariant检查测试代码 ≠ 生产代码— 只存在于测试文件的函数不会随 SDK 发布Flutter 继承自原生— 其“支持”取决于它要求的 iOS / Android SDK 版本先搜存量 Issue— 创建新 GitHub Issue 之前对比工具函数实现—canActivateRepeatedly等函数在各 SDK 逻辑可能不同浏览器是真相源内置 UI ≠ delegate— iOS、React Native、Flutter 有内置问卷渲染Android 仅 delegate无内置 UI。Android 显示模型暴露字段即足够issue: false对有内置渲染的 SDK渲染代码必须真正使用该字段检查渲染代码而非仅模型— 例如 iOS 在PostHogDisplayChoiceQuestion上暴露了shuffleOptions但 SwiftUI 的QuestionTypes.swift渲染选项时完全忽略了它。这 9 条陷阱不是理论说教而是可从真实数据中验证的规律例如 surveyVersionRequirements.ts 中 “Shuffle choice options” 对 Android 标注// delegate pattern - no built-in UI; flag exposed on display model并设issue: false而 iOS 同样暴露了该字段却因为渲染代码未使用而被挂上 issue —— 两条记录恰好演示了第 8、9 条陷阱的正确处置方式。十一、审计后的技能自改进Post-Audit每次审计完成后可评估是否有值得沉淀回技能文件的经验发现的新陷阱— 补充进 Common Pitfalls 章节识别出的新关键文件— 补充进 Step 5 的文件路径清单可对比的新工具函数— 补充进 “Key utility functions” 列表模式变化— 若 SDK 实现结构调整更新对应路径。若确有改进向用户提出如下建议不得直接改动技能文件I found some learnings during this audit that could improve the skill: - [describe the improvement] Would you like me to update the skill file?【免费下载链接】posthog:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.项目地址: https://gitcode.com/GitHub_Trending/po/posthog创作声明:本文部分内容由AI辅助生成(AIGC),仅供参考
返回列表