Epic 1 - Story 3 - Add Ability to Retrieve Pokemon Details From API Service and Return Subset on our Apis

[Sifou13]

Following the design and decision made on the Architecture and framework to use, and that the initial backbone has been setup and checked in, there should not be much plumming to do and the task could be given to a more junior member of he team to work on, and purely focus on the functional requirements, while most of the technical requirements should be in place, without being ever set in stones as things can change.

Given the API skeleton available, this task should be comprise of the following:

• Implement and unit test the service that retrieves pokemon from the following API: https://pokeapi.co/ (bare in mind that the provider could change URL as well as we could decide to go for another provider or develop our own.
• Integrate the service with the API project so that the API returns the following subset of Pokemon properties/details: Name (Text), Description (Text), Habitat (Text) and IsLegendaryStatus (Boolean)
• Update Docker File to include the service project

[Sifou13]

Initial Prototype enhancement and first feature added

Manually and unit testing

Picked up during this task: More hardening to come (Framework UT) + Review logical services and refactor according to SOLID + Volatility - This is fine since still prototyping / refactoring for first release and Repo still private (to this day)