-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create API to Get Event Records #43
Comments
Can I handle this task? |
Hey! I'm Jan. • Dojo |
Mind if I try this one? |
Could I take on this issue? |
Could I try solving this? |
Hey there! I’m Uche, a frontend developer with a solid grasp of backend principles, particularly when it comes to API design and performance optimization. For this task, I’d approach it as follows: Implement a GET API route to retrieve event records from the database, ensuring it supports filtering by event categories, date range, and user participation. Optimize the query to handle large datasets efficiently, potentially using techniques like pagination, indexing, and caching to ensure scalability and performance. Structure the JSON response to include relevant event details, such as the event name, date, category, and user registration status, ensuring the data is clear and organized. Handle status codes correctly, ensuring users receive meaningful responses, like 200 OK for success, 404 Not Found if no events match the filter, and 500 Internal Server Error for any unforeseen issues. Ensure the API is built to scale as the event dataset grows, keeping performance in mind. I’m confident I can deliver a solid API that meets all the requirements and delivers a great experience for users. ETA: 24 HOURS Looking forward to taking on this task! |
Could I grab this task? |
Can I take this issue? |
@Ibinola assigned, please join the Telegram group; https://t.me/explorebeyondzerocheck |
Description:
Develop an API endpoint to retrieve stored event records, allowing users to view upcoming events and past events they have registered for.
Requirements:
Acceptance Criteria:
ETA 48 hours
The text was updated successfully, but these errors were encountered: