SpaceX-API VS space-x-app

SpaceX REST API

This is what i meant by that explanation. In this project we will make a request to a SpaceX API and the results we want from the huge chunk of data we will be receiving from the API are: id of type string, flight_number of type int, name and details of type string and success of type boolean.

This is a cool api, spacex posts all of their flight info on here, and there's no auth which might make it easier for testing/learning: https://github.com/r-spacex/SpaceX-API

I like this unofficial SpaceX API. I am using it in examples for API-related tutorials and to train less experience technical personnel. Works like a charm so far :)

5. SpaceX API

Here's one that I've made showing all the active boosters using the unofficial SpaceX API

To display the next scheduled launch date, we have to fetch our data from the API. Therefore we will use the following API Documentation spacexdata.com API.

Github: https://github.com/tipenehughes/space-x-app

https://github.com/tipenehughes/space-x-app/blob/master/src/Components/Landing/Landing.js#L47

This (https://github.com/tipenehughes/space-x-app/blob/master/src/Components/VehicleSpecs/Vehicles/Falconheavy.js#L17) pattern / making assumptions of the exact position of data is bad. Your UI components should be trivial and only know how to render DOM with the exact data necessary or fetch its exact data itself. Otherwise the parent should manage providing the exact, narrowly scoped, data requirements of the component