the-benchmarker / the-benchmarker/web-frameworks

Make frameworks URL consistent for the exposed data

Open
#4,236 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
7.1k
Forks
732
Avg merge
11h 42m
Merged PRs (30d)
141

Description

For the exposed data (data.json and data.min.json), some frameworks uses their own web page as the framework URL (e.g. Fiber framework URL is https://gofiber.io/), and some frameworks uses their repository URL as the framework URL (e.g. Mark framework URL is https://github.com/passwalls/mark).

It will be nice to make all of the frameworks URL consistent and use the repository URL (whether it's GitHub or other VC) as the framework URL. This allows the website to easily fetches repository information from GitHub API (If the framework's repository are hosted in GitHub, which seems like most of them are)

For example fiber framework URL will be https://github.com/gofiber/fiber. I can easily extract the author / org name and repo name (gofiber/fiber) to fetch information from GitHub API -> https://api.github.com/repos/gofiber/fiber

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the exposed data in data.json and data.min.json and compare framework URL values such as Fiber and Mark. Trace where those records are maintained or generated, then update the source so every framework uses its repository URL, including non-GitHub repositories where applicable. Verify that both exposed data files consistently contain the repository URLs.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
data
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.