Stop polluting configuration object in w3c/headers.js
Open
Nobody has claimed this yet.
refactoring
- Dominant language
- JavaScript
- Stars
- 806
- Forks
- 434
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 32
Description
Currently it pollutes the configuration object only to pass them to templates. They should be instead passed as a dictionary object.
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
Read w3c/headers.js first and trace how configuration values reach the templates. Confirm where the configuration object is mutated and define the dictionary boundary for passing those values. Done means templates receive the needed values without polluting the configuration object.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100