feat: allow renaming/updating an existing study chapter's title
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api
Research direction
Start by reading the existing POST /api/study/{studyId}/{chapterId}/tags endpoint documentation and examples. Determine whether the chapter name belongs as an optional parameter there or in a dedicated endpoint, then verify that a supplied name changes the displayed title while existing PGN tag updates continue to work.
Written by the indexing model from the issue text.
Description
POST /api/study/{studyId}/{chapterId}/tags updates PGN tags but not the chapter's displayed title.
I would a way to rename an existing chapter, e.g. an optional name param on /tags, or a dedicated POST /api/study/{studyId}/{chapterId}/name.
- Dominant language
- TypeScript
- Stars
- 599
- Forks
- 174
- Avg merge
- 21h 21m
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 lichess-org/api
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lichess-org/api#678 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
lichess-org/api#637 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
lichess-org/api#673 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
lichess-org/api#657 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
lichess-org/api#654 · 1 comment ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
callstackincubator/rozenite#518 ·
Maintainers usually reply within 1 day
-
Area/Workflow Priority/Blocker Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
wso2/product-integrator#2622 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
area:bash bug has repro platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anthropics/claude-code#98644 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
allure-framework/allure-js#1603 ·
Maintainers usually reply within 1 day