Endpoints:

/api/banned for display banned pokemons /api/banned/store for store pokemon (fetch data from api by pokemon name)

name: required

/api/banned/{id} for destroy pokemon

id: required

/api/info?names=... for display specific pokemons data

?names: required, string

/api/custom for display custom pokemons data /api/custom/store for create custom pokemon

fields
• name: required, string
• description: nullable, string
• height: required, integer
• weight: required, integer
• damage: required, integer
• type: required, string

/api/custom/update/{id}

fields
• name: required, string
• description: nullable, string
• height: required, integer
• weight: required, integer
• damage: required, integer
• type: required, string

/api/custom/destroy/{id}

id: required

Deploy:

1. git clone git@github.com:patryk-lukasz-kacprowicz/PokeWiki.git
2. composer install --optimize-autoloader
3. cp .env.example .env
4. php artisan key:generate
5. Configure database data in .env file
6. Configure secret key in .env file
7. php artisan migrate

How the code works

Data retrieval from the API works on a search basis. If the user selects a Pokémon that is not in the database but exists in the API, it will first be added to the database and then its data will be displayed.