(GraphQL) Add the event resolver for discounts
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 75/100
Research direction
Start on the graphql-v2 branch by reading graphql/README.md and comparing the rooms object implementation. Inspect schema.graphqls and discounts.resolvers.go to understand the existing GraphQL patterns. Done means the discounts object is defined in schema.graphqls and its events resolver is implemented in discounts.resolvers.go.
Written by the indexing model from the issue text.
Description
Overview
Follow the guidelines on GraphQL implementation.
Add the discounts object in schema.graphqls and the discounts events resolver in discounts.resolvers.go for branch graphql-v2
Since discounts don't reference another object, there's no need for separation of concerns. We can combine the database object and GraphQL object with @goTag. See the rooms object for reference.
Resources
Graphql README.md
Intro to Graphql
Graphql and gqlgen Notes
gqlgen docs
- 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 33 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 12 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 19 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
-
[doc-healer] DDUw improvement: retry integrity-filtered issue reads with direct single-item lookupsOpenautomation documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
containerd/containerd#14476 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
Infisical/infisical#8987 · 1 comment ·
Maintainers usually reply within 1 day
-
scan framework and scan control accept empty and whitespace-only policy names in Args validationPossibly taken @WKr1shna claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day