oslabs-beta / oslabs-beta/TrailGuide
Metrics Evaluation
Open
Nobody has claimed this yet.
question
- Dominant language
- TypeScript
- Stars
- 28
- Forks
- 0
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Problem: Current efficiency of the app is clunky. Without metrics to support the current status, we have nothing to reference.
Solution: Using tools for metrics exploration in the browser, can can track and document our current efficiency status in each area of our app. This will provide information on where to look to reevaluate and make improvements in the codebase.
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
The issue names no files, tests, or entry points. Start by identifying the app areas whose efficiency should be measured and the browser metrics tooling to use, then define the baseline documentation and concrete completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100