To start your journey you will be creating an API that allows a user to create and care for a virtual pet, reminiscent of a Tamagachi. The basic functionality will walk you through the 4 basic parts of a web api, create, read, update and delete. For explorer mode, keep it simple and they add features.
Objectives
Create an API that can CRUD against a Database
practice creating ASP.NET Web API endpoints
practice EF Core.
Requirements
Create a simple API that has a handful of endpoints to manage data
The API should be using Web API Controllers, Ef Core, and Postgres database
Install the sdg-api template using the command dotnet new -i SDG.templates.Web.API
Explorer Mode
Create and new sdg-api that has the following features
a database with 1 table, called Pets.
Should use a POCO called Pet with the following columns:
Id (int)
Name (string)
Birthday (DateTime)
DeathDate (DateTime?)
HungerLevel (int)
HappinessLevel (int)
Your API should have the following endpoints
[x] GET /api/pets, this should return all pets in your database.
[x] GET /api/pets/{id}, This should return the pet with the corresponding Id.
[x] POST /api/pets, This should create a new pet. The body of the request should contain the name of the pet.
[x] PUT /api/pets/{id}/play, This should find the pet by id, and add 5 to its happiness level and add 3 to its hungry level
[x] PUT /api/pets/{id}/feed, This should find the pet by id, and remove 5 from its hungry level and add 3 to its happiness level.
[x] PUT /api/pets/{id}/scold, This should find the pet by id, and remove 5 from its happiness level
[x] DELETE /api/pets/{id}, this should delete a pet from the database by Id
Adventure Mode
Add the following features to your API
Add a column to your pet model call IsDead (bool). Whenever you call a PUT to update a pet, give your pet a 10% chance of Dying.
Add a LastInteractedWithDate(DateTime), that gets updated every time a pet is queried from the database on PUT or a GET. If the LastInteractedWithDate is ever over 3 days, the pet should die from neglect.
Add an endpoint that gets Pets that are only alive
Create a console app that interacts with your API that:
alexalewis
commented
4 years ago
The Rise of the Tamagotchi
To start your journey you will be creating an API that allows a user to create and care for a virtual pet, reminiscent of a Tamagachi. The basic functionality will walk you through the 4 basic parts of a web api, create, read, update and delete. For explorer mode, keep it simple and they add features.
Objectives
Requirements
sdg-apitemplate using the commanddotnet new -i SDG.templates.Web.APIExplorer Mode
Create and new
sdg-apithat has the following featuresa database with 1 table, called
Pets.Petwith the following columns:Your API should have the following endpoints
GET /api/pets, this should return all pets in your database.GET /api/pets/{id}, This should return the pet with the corresponding Id.POST /api/pets, This should create a new pet. The body of the request should contain the name of the pet.PUT /api/pets/{id}/play, This should find the pet by id, and add 5 to its happiness level and add 3 to its hungry levelPUT /api/pets/{id}/feed, This should find the pet by id, and remove 5 from its hungry level and add 3 to its happiness level.PUT /api/pets/{id}/scold, This should find the pet by id, and remove 5 from its happiness levelDELETE /api/pets/{id}, this should delete a pet from the database by IdAdventure Mode
Add the following features to your API
IsDead(bool). Whenever you call a PUT to update a pet, give your pet a 10% chance of Dying.LastInteractedWithDate(DateTime), that gets updated every time a pet is queried from the database on PUT or a GET. If theLastInteractedWithDateis ever over 3 days, the pet should die from neglect.Create a console app that interacts with your API that:
Epic mode
Resources