micro-analytics / micro-analytics/micro-analytics-cli
favicon.ico
Open
Nobody has claimed this yet.
discussion
- Dominant language
- JavaScript
- Stars
- 732
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
I've been using chrome to open up views to test and it's requesting for favicon.ico. Is there something we could/should do here? I think this could be a common usage pattern for people trying out the project/testing it.
So some sort of filtering or blacklist?
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 file or test is named. Start by tracing how the service handles requests for favicon.ico and review the existing filtering or blacklist behavior. Done should mean the browser request is handled according to a documented, tested rule without disrupting normal analytics requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100