Create the Scholarship schema
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by reading discussion #327 and the existing schema definitions in the repository to find where the Scholarship schema belongs. Confirm the unresolved field types, especially immigration_status and min_gpa, then add the schema with the listed nested requirements and renewal fields and verify it fits the API's existing schema conventions.
Written by the indexing model from the issue text.
Description
Overview
Add the Scholarship schema from discussion #327 as this helps unblock https://github.com/UTDNebula/api-tools/issues/83
Scholarship = {
"id": number,
"name": string,
"description": string,
"deadline": string,
"term": string,
"contact": string,
"application_instructions": string,
"application_link": string,
"requirements" : {
"matriculation_status": string,
"immigration_status": enum,
"texas_residency_status": string,
"course_load": string,
"eligible_classification": string,
"min_gpa": string // or double ?
"schools": string[],
"majors": string[],
"concentrations": string[],
}
"renewal": string
}
- Dominant language
- Go
- Stars
- 41
- Forks
- 100
- Avg merge
- 8d 20h
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No 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 UTDNebula/nebula-api
-
Serve API docs on the root routePossibly taken @krish-gnani claimed this 30 days ago. Openduplicate L1 recommended for recruits
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
UTDNebula/nebula-api#430 · 1 comment · 1 assignee ·
Maintainers usually reply within 3 days
-
L1
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
UTDNebula/nebula-api#421 · 1 comment · 1 reaction ·
Maintainers usually reply within 3 days
-
L1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UTDNebula/nebula-api#415 ·
Maintainers usually reply within 3 days
-
Sentry - runtime.boundsError: runtime error: index out of range [0] with length 0Possibly taken @IriqGx claimed this 9 days ago. Openbug report good first issue L1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UTDNebula/nebula-api#411 · 8 comments · 1 assignee ·
Maintainers usually reply within 3 days
-
Fix unclear error when clubs db uri is missing or emptyPossibly taken @Ganesh-Sarikonda claimed this 17 days ago. Opengood first issue L1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UTDNebula/nebula-api#379 ·
Maintainers usually reply within 3 days
All issues in UTDNebula/nebula-api
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 1 day
-
stage-fail
Difficulty 1/5 Under an hour Newbie friendliness 72/100
siyuan-note/bazaar#2405 ·
Maintainers usually reply within 1 day
-
bug priority: high workstream:cache
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rossoctl/context-guru#707 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
prime-radiant-inc/evener#5028 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day