Prompt for the LanguageApp

Please create a React-JS application for the LanguageModule. The application  has to offer the following views for the user interface: 
    1. LanguageView 
    2. PeeringAgreementView 
    3. ServiceLanguageView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The LanguageView must contain the following fields: 
    - name: IsoCode   type: STRING 
    - name: Name   type: STRING 
    - name: Notes   type: STRING 
An existing Language entity should be loaded from the relative URL: 
    "/LanguageService/language/{id}"   (HTTP-GET) 
If a new Language entity has been created, the new entity should be posted to the relative URL: 
    "/LanguageService/language"   (HTTP-POST) 
If an existing Language entity has been updated, the modified entity should be sent to the relative URL: 
    "/LanguageService/language/{id}"   (HTTP-PUT) 
If an existing Language entity has to be deleted, the following relative URL should be called: 
    "/LanguageService/language/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ServiceLanguage columns: 
    - column: Language 
    - column: ServiceSupply 
    - column: AvailabilityType 
The table should have the title "ServiceLanguages" und the data must be loaded from the server with the following relative URL: 
    "/LanguageService/servicelanguage/language/{id}"

2. The PeeringAgreementView must contain the following fields: 
    - name: EndDate   type: DATE 
    - name: InternetServiceProvider   type: InternetServiceProvider 
    - name: Notes   type: STRING 
    - name: ServiceSupply   type: ServiceSupply 
    - name: StartDate   type: DATE 
The data source for the [ServiceSupply] select control should be loaded from the relative URL: 
    "/ServiceSupplyService/servicesupply"   (HTTP-GET) 
The data source for the [InternetServiceProvider] select control should be loaded from the relative URL: 
    "/CountryService/internetserviceprovider"   (HTTP-GET) 
An existing PeeringAgreement entity should be loaded from the relative URL: 
    "/LanguageService/peeringagreement/{id}"   (HTTP-GET) 
If a new PeeringAgreement entity has been created, the new entity should be posted to the relative URL: 
    "/LanguageService/peeringagreement"   (HTTP-POST) 
If an existing PeeringAgreement entity has been updated, the modified entity should be sent to the relative URL: 
    "/LanguageService/peeringagreement/{id}"   (HTTP-PUT) 
If an existing PeeringAgreement entity has to be deleted, the following relative URL should be called: 
    "/LanguageService/peeringagreement/{id}"   (HTTP-DELETE)

3. The ServiceLanguageView must contain the following fields: 
    - name: AvailabilityType   type: STRING 
    - name: Language   type: Language 
    - name: ServiceSupply   type: ServiceSupply 
The data source for the [ServiceSupply] select control should be loaded from the relative URL: 
    "/ServiceSupplyService/servicesupply"   (HTTP-GET) 
The data source for the [Language] select control should be loaded from the relative URL: 
    "/LanguageService/language"   (HTTP-GET) 
An existing ServiceLanguage entity should be loaded from the relative URL: 
    "/LanguageService/servicelanguage/{id}"   (HTTP-GET) 
If a new ServiceLanguage entity has been created, the new entity should be posted to the relative URL: 
    "/LanguageService/servicelanguage"   (HTTP-POST) 
If an existing ServiceLanguage entity has been updated, the modified entity should be sent to the relative URL: 
    "/LanguageService/servicelanguage/{id}"   (HTTP-PUT) 
If an existing ServiceLanguage entity has to be deleted, the following relative URL should be called: 
    "/LanguageService/servicelanguage/{id}"   (HTTP-DELETE)