Please stick to the following instructions on how to submit your application:
- Read the whole README
- Create a new repository on your Github Account. Note: The repository has to be public.
- Add your solution with all requirements to your repository
- Send a mail to [email protected] with following information:
- Your Name
- Link to public accessable repository on GitHub
- How many hours it took to complete (roughly)
Please do not spend much more than 6 hours for the whole task. This is not a hard limitation but want to respect your time since we cannot hire every applicant. Also only start with the task if you think this is something you can do in the given time frame.
- Make sure that your repository is public
- Only an application with all requirements can be considered
- Provide setup process if required
- Copied structures or code from other applications will be completely ignored
Thank you very much and have fun with the challenge!
Develop a minified version of the Events module API based on wireframes. The API should provide endpoints for events CRUD.
It also should enable users to register for the the event.
- You do not have to build the frontend. Only the API requests that would enable the frontend to work.
- Top navigation, menu on the left, etc. are not part of this task. This is only about the events module.
- Pagination should be added in GET all events to enable loading more events
- For API design follow REST style
- Project
- ASP.NET Core web API application. Prefer version 6.
- Database
- Use SQLite or MySQL (Do not use Microsoft SQL or SQL Express). Please add setup instructions if necessary
- Use EF Core ORM framework to work with database
- Tests project
- At least one unit test should be written (even the simplest one)
- Project should be setup to run as a docker container -
Dockerfile
is required - Attach user data
- To get complete single event page response - it should include the user data as on the mockup. Make an API request to user API to get user info (https://jsonplaceholder.typicode.com/users/1)
- Use caching
- Use Rich domain model
- Add a diagram of the solution in Miro, attach screenshot in repository
- Cover solution classes with unit tests
❗ Please add instructions for setup if necessary
Implement invitations management mechanics:
Event creator should be able to invite participants. Then, after approval, the invited user will become an event participant.
❗No need to implement user management endpoints like fetching all users. Assume frontend will work with users API and send you selected userIds.