Common adoption pitfalls
Most missing or misplaced markers come from identifiers, hidden UI, routing, or unstable Adapter references.
Tip
Help me follow the Common adoption pitfalls guide. Most missing or misplaced markers come from identifiers, hidden UI, routing, or unstable Adapter references. Review the current project and turn this guidance into concrete next steps.
Edge cases
| Topic | Response |
|---|---|
| Missing id | Add data-report-id to the selectable root |
| Duplicate id | Use a stable unique id per item |
| group ↔ item change | Check existing marker restoration |
| Modal or tab | Use matching data-fp-view and data-fp-open values |
| SPA routing | Use onNavigate and pathname scope |
| Production-built staging | Confirm devOnly behavior |
| Inline Adapter | Keep it stable with useMemo or module scope |
| Version change | Agree on data-scope behavior |
Before rollout
- Storage mode
- project.id / env / version
- Initial tagging scope
- Modal and tab attribute strategy
- Cross-page onNavigate
- Production visibility
