[feature]:Library Demo Enhancement to add CRUD Operations
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18.5k
- Forks
- 2.4k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 101
Description
Issue Description: GraphQL CRUD for Library Demo
🔖 Enhancement description Currently, the Library Demo application is a read-only GraphQL service. I propose introducing CRUD (Create, Read, Update, Delete) capabilities through GraphQL Mutations.
Proposed improvements:
GraphQL Mutations: Add addBook, updateBook, deleteBook, addAuthor, and deleteAuthor operations.
DTO Implementation: Introduce BookInput and AuthorInput for secure and clean data handling.
🎤 Why should this be worked on? A read-only API limits the utility of a library management system. Adding CRUD operations allows for dynamic data management and provides a complete example of GraphQL usage.
Team: Team 137 GDG CHARUSAT 💻 Repository:
hindochahitarth/samples-java
Contributor 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.
Research direction
Start by locating the Library Demo application and its existing read-only GraphQL service. Review how books and authors are currently represented, then determine where BookInput, AuthorInput, and the addBook, updateBook, deleteBook, addAuthor, and deleteAuthor mutations belong. Done means the proposed CRUD operations are available through GraphQL with secure DTO handling and appropriate verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100