snowplow / snowplow/snowplow-javascript-tracker
Explore internal tracker logging with trackError
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 590
- Forks
- 232
- Avg merge
- 2h 22m
- Merged PRs (30d)
- 3
Description
This is superior of https://github.com/snowplow/snowplow-javascript-tracker/issues/556.
We can check for invalid tracker state and use trackError (or even introduce special schema) to warn user (user installed tracker, not end-user) that tracker is in invalid state or some exception occur. Unlike console.log approach which will be observed only by end-user (which is undesirable) trackError approach has more chances to be observed by right person.
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
No files, tests, or entry points are named. Start by reading superseded issue 556 and tracing the existing trackError path; clarify whether invalid tracker states and exceptions should use it or a special schema, with completion defined as warnings reaching the tracker user rather than the end-user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100