sitespeedio / sitespeedio/sitespeed.io
[Feature] Add a flag opposite to userTimingWhitelist to specify what to block.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5k
- Forks
- 624
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 2
Description
Feature/improvement
Original flag for idea: --userTimingWhitelist
It looks more convenient to block some special metrics from Google, Facebook, and so on. The weak point of whitelist that we can easily miss a new or unexpected metrics.
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 by tracing how the existing --userTimingWhitelist flag is parsed and how user timing metrics are filtered. Add the opposite block-list behavior without changing the existing whitelist behavior, and verify that named metrics are excluded while other metrics remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100