Convert "ignore" into a nesting mode, and add variants.
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 72
- Forks
- 10
- Avg merge
- 9d 15h
- Merged PRs (30d)
- 3
Description
Right now we have containertiming-ignore and containertiming-nesting strategy. I think you could just merge these together as a single "nesting strategy" but help disambiguate "ignore" mode.
I think there are two forms of "ignore":
- "Not interested in any timings, for self or ancestors" (performance optimization?)
- "This is a container root, and I don't want to report paints up" ("isolated" component or something?)
Consider using names such as: disabled and private to differentiate (bikeshed!).
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 comparing the existing containertiming-ignore and containertiming-nesting strategies with the two proposed ignore meanings. The issue needs a maintainer-approved distinction and names such as disabled and private before implementation can be scoped; done means the nesting strategy variants and their semantics are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100