Automattic / Automattic/wp-calypso
Launchpad: Centralize the `calypso_launchpad_task_missing_calypso_path` log
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.6k
- Forks
- 2k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 552
Description
### Details
Currently, we are logging all launchpad tasks without a calypso_path with the `calypso_launchpad_task_missing_calypso_path` event, but it is only happening on the customer-home launchpad, but not on the onboarding launchpad.
We should review this log is still required, if we can make it part of the task_view event or centralize it in a single place to support both flows.
More info on this comment.
https://github.com/Automattic/wp-calypso/pull/87141/files#r1489971951
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the referenced comment and files in pull request #87141, then trace where `calypso_launchpad_task_missing_calypso_path` is emitted in the customer-home and onboarding launchpad flows. Determine whether the event should remain separate or be covered by `task_view`; done means the chosen logging behavior is centralized and applies consistently to both flows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability-sre
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100