Prompt for the DrmSchemeApp

Please create a React-JS application for the DrmSchemeModule. The application  has to offer the following views for the user interface: 
    1. ChannelSubscriptionView 
    2. DrmSchemeView 
    3. TitleDrmSchemeView 
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 ChannelSubscriptionView must contain the following fields: 
    - name: AutoRenew   type: BOOL 
    - name: Channel   type: Channel 
    - name: EndDate   type: DATE 
    - name: StartDate   type: DATE 
    - name: Status   type: STRING 
    - name: User   type: User 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserService/user"   (HTTP-GET) 
The data source for the [Channel] select control should be loaded from the relative URL: 
    "/ChannelService/channel"   (HTTP-GET) 
An existing ChannelSubscription entity should be loaded from the relative URL: 
    "/DrmSchemeService/channelsubscription/{id}"   (HTTP-GET) 
If a new ChannelSubscription entity has been created, the new entity should be posted to the relative URL: 
    "/DrmSchemeService/channelsubscription"   (HTTP-POST) 
If an existing ChannelSubscription entity has been updated, the modified entity should be sent to the relative URL: 
    "/DrmSchemeService/channelsubscription/{id}"   (HTTP-PUT) 
If an existing ChannelSubscription entity has to be deleted, the following relative URL should be called: 
    "/DrmSchemeService/channelsubscription/{id}"   (HTTP-DELETE)

2. The DrmSchemeView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing DrmScheme entity should be loaded from the relative URL: 
    "/DrmSchemeService/drmscheme/{id}"   (HTTP-GET) 
If a new DrmScheme entity has been created, the new entity should be posted to the relative URL: 
    "/DrmSchemeService/drmscheme"   (HTTP-POST) 
If an existing DrmScheme entity has been updated, the modified entity should be sent to the relative URL: 
    "/DrmSchemeService/drmscheme/{id}"   (HTTP-PUT) 
If an existing DrmScheme entity has to be deleted, the following relative URL should be called: 
    "/DrmSchemeService/drmscheme/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following TitleDrmScheme columns: 
    - column: Title 
    - column: DrmScheme 
The table should have the title "TitleDrmSchemes" und the data must be loaded from the server with the following relative URL: 
    "/DrmSchemeService/titledrmscheme/drmscheme/{id}"

3. The TitleDrmSchemeView must contain the following fields: 
    - name: DrmScheme   type: DrmScheme 
    - name: Title   type: Title 
The data source for the [DrmScheme] select control should be loaded from the relative URL: 
    "/DrmSchemeService/drmscheme"   (HTTP-GET) 
The data source for the [Title] select control should be loaded from the relative URL: 
    "/TitleService/title"   (HTTP-GET) 
An existing TitleDrmScheme entity should be loaded from the relative URL: 
    "/DrmSchemeService/titledrmscheme/{id}"   (HTTP-GET) 
If a new TitleDrmScheme entity has been created, the new entity should be posted to the relative URL: 
    "/DrmSchemeService/titledrmscheme"   (HTTP-POST) 
If an existing TitleDrmScheme entity has been updated, the modified entity should be sent to the relative URL: 
    "/DrmSchemeService/titledrmscheme/{id}"   (HTTP-PUT) 
If an existing TitleDrmScheme entity has to be deleted, the following relative URL should be called: 
    "/DrmSchemeService/titledrmscheme/{id}"   (HTTP-DELETE)