Switch to org & site throughout
Open
dev
question
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 11
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 7
Description
We've already started switching admin API responses from owner & repo to org & site to comply with hlx5 concepts. However internally, we are still dealing with owner & repo. Should we take it all the way?
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by searching the repository for internal uses of owner and repo, then compare them with the admin API responses already using org and site. Done requires a decided migration scope and consistent terminology wherever the change is approved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100