Absence field in GET /Activity needed
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- api
Research direction
Start with the GET /Activity endpoint definition and its response schema in the repository. Determine where activity fields are specified, then add the absence indicator consistently and verify the response examples or API checks show whether an activity was marked as an absence.
Written by the indexing model from the issue text.
Description
It would be useful to know if a certain activity was marked as an "absence"
- Dominant language
- No language data
- Stars
- 49
- Forks
- 47
- Avg merge
- 1h 1m
- Merged PRs (30d)
- 1
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 Tripletex/tripletex-api2
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Tripletex/tripletex-api2#135 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Tripletex/tripletex-api2#133 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Tripletex/tripletex-api2#130 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Tripletex/tripletex-api2#127 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Tripletex/tripletex-api2#126 · 1 reaction ·
All issues in Tripletex/tripletex-api2
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openzim/mwoffliner#2933 ·
Maintainers usually reply within 1 day
-
Use the README category name for website links and submissionsPossibly taken @dajiaohuang claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
birobirobiro/awesome-shadcn-ui#647 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Urigo/accounter-fullstack#4604 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
kagent-dev/tools#87 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
micronaut-projects/micronaut-core#13677 ·
Maintainers usually reply within 1 day