Prompt for the FeatureFlagApp

Please create a React-JS application for the FeatureFlagModule. The application  has to offer the following views for the user interface: 
    1. FeatureFlagView 
    2. LocationView 
    3. StoryViewView 
    4. UserFeatureFlagView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The FeatureFlagView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: Description   type: STRING 
    - name: IsGlobalEnabled   type: BOOL 
    - name: Name   type: STRING 
An existing FeatureFlag entity should be loaded from the relative URL: 
    "/FeatureFlagService/featureflag/{id}"   (HTTP-GET) 
If a new FeatureFlag entity has been created, the new entity should be posted to the relative URL: 
    "/FeatureFlagService/featureflag"   (HTTP-POST) 
If an existing FeatureFlag entity has been updated, the modified entity should be sent to the relative URL: 
    "/FeatureFlagService/featureflag/{id}"   (HTTP-PUT) 
If an existing FeatureFlag entity has to be deleted, the following relative URL should be called: 
    "/FeatureFlagService/featureflag/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserFeatureFlag columns: 
    - column: IsEnabled 
    - column: CreatedAt 
    - column: UserAccount 
    - column: FeatureFlag 
The table should have the title "UserFeatureFlags" und the data must be loaded from the server with the following relative URL: 
    "/FeatureFlagService/userfeatureflag/featureflag/{id}"

2. The LocationView must contain the following fields: 
    - name: Address   type: STRING 
    - name: City   type: STRING 
    - name: Country   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: Latitude   type: STRING 
    - name: Longitude   type: STRING 
    - name: Name   type: STRING 
An existing Location entity should be loaded from the relative URL: 
    "/FeatureFlagService/location/{id}"   (HTTP-GET) 
If a new Location entity has been created, the new entity should be posted to the relative URL: 
    "/FeatureFlagService/location"   (HTTP-POST) 
If an existing Location entity has been updated, the modified entity should be sent to the relative URL: 
    "/FeatureFlagService/location/{id}"   (HTTP-PUT) 
If an existing Location entity has to be deleted, the following relative URL should be called: 
    "/FeatureFlagService/location/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Post columns: 
    - column: Location 
    - column: IsSponsored 
    - column: CreatedAt 
    - column: Visibility 
    - column: Caption 
    - column: UserAccount 
    - column: UpdatedAt 
    - column: IsArchived 
    - column: MediaType 
The table should have the title "Posts" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/post/location/{id}"

3. The StoryViewView must contain the following fields: 
    - name: Story   type: Story 
    - name: ViewedAt   type: DATE 
    - name: Viewer   type: UserAccount 
The data source for the [Viewer] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
The data source for the [Story] select control should be loaded from the relative URL: 
    "/StoryService/story"   (HTTP-GET) 
An existing StoryView entity should be loaded from the relative URL: 
    "/FeatureFlagService/storyview/{id}"   (HTTP-GET) 
If a new StoryView entity has been created, the new entity should be posted to the relative URL: 
    "/FeatureFlagService/storyview"   (HTTP-POST) 
If an existing StoryView entity has been updated, the modified entity should be sent to the relative URL: 
    "/FeatureFlagService/storyview/{id}"   (HTTP-PUT) 
If an existing StoryView entity has to be deleted, the following relative URL should be called: 
    "/FeatureFlagService/storyview/{id}"   (HTTP-DELETE)

4. The UserFeatureFlagView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: FeatureFlag   type: FeatureFlag 
    - name: IsEnabled   type: BOOL 
    - name: UserAccount   type: UserAccount 
The data source for the [FeatureFlag] select control should be loaded from the relative URL: 
    "/FeatureFlagService/featureflag"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserFeatureFlag entity should be loaded from the relative URL: 
    "/FeatureFlagService/userfeatureflag/{id}"   (HTTP-GET) 
If a new UserFeatureFlag entity has been created, the new entity should be posted to the relative URL: 
    "/FeatureFlagService/userfeatureflag"   (HTTP-POST) 
If an existing UserFeatureFlag entity has been updated, the modified entity should be sent to the relative URL: 
    "/FeatureFlagService/userfeatureflag/{id}"   (HTTP-PUT) 
If an existing UserFeatureFlag entity has to be deleted, the following relative URL should be called: 
    "/FeatureFlagService/userfeatureflag/{id}"   (HTTP-DELETE)