🚀 Feature: mark cli API as stable
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- javascript, typescript
- Domain
- cli
Research direction
This is a discussion issue rather than a scoped change: first find where the CLI prints the experimental-API warning (search the source for the warning text) and identify the public API entry point it refers to. Read the TypeScript rewrite status in the repository before deciding whether the warning can be removed. Done would mean maintainers agree on a stability definition and the warning/docs are updated accordingly; no implementation should start until that decision is recorded.
Written by the indexing model from the issue text.
Description
Feature Request Checklist
- I have searched for related issues and found none that matched my issue.
Overview
Currently our API triggers a warning (which is quite old) about it being experimental. Thoughts on when we should consider it stable? I'm thinking after the TypeScript rewrite. @all-contributors/maintainers what do y'all think?
Additional Info
No response
- Dominant language
- JavaScript
- Stars
- 427
- Forks
- 157
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 57
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from all-contributors/cli
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
all-contributors/cli#690 ·
Maintainers usually reply within 1 day
-
status: in discussion type: infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
all-contributors/cli#670 ·
Maintainers usually reply within 1 day
-
type: admin
Difficulty 5/5 Over a week Newbie friendliness 12/100
all-contributors/cli#685 ·
Maintainers usually reply within 1 day
-
status: in discussion type: infrastructure
Difficulty 1/5 Under an hour Newbie friendliness 35/100
all-contributors/cli#672 ·
Maintainers usually reply within 1 day
-
status: in discussion type: feature
Difficulty 4/5 3-5 days Newbie friendliness 45/100
all-contributors/cli#671 ·
Maintainers usually reply within 1 day
All issues in all-contributors/cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area: ui Bug Payload OSS
Difficulty 1/5 Under an hour Newbie friendliness 88/100
payloadcms/payload#19839 ·
Maintainers usually reply within 1 day
-
Add: C+ ClassicsOpenapproved channels:add check:passed
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
AllTheMods/ATM10-Aeronautics#167 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day