Prompt for the HashtagApp

Please create a React-JS application for the HashtagModule. The application  has to offer the following views for the user interface: 
    1. HashtagView 
    2. TweetHashtagView 
    3. UserBlockView 
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 HashtagView must contain the following fields: 
    - name: CreatedAt   type: STRING 
    - name: Description   type: STRING 
    - name: Tag   type: STRING 
An existing Hashtag entity should be loaded from the relative URL: 
    "/HashtagService/hashtag/{id}"   (HTTP-GET) 
If a new Hashtag entity has been created, the new entity should be posted to the relative URL: 
    "/HashtagService/hashtag"   (HTTP-POST) 
If an existing Hashtag entity has been updated, the modified entity should be sent to the relative URL: 
    "/HashtagService/hashtag/{id}"   (HTTP-PUT) 
If an existing Hashtag entity has to be deleted, the following relative URL should be called: 
    "/HashtagService/hashtag/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following TweetHashtag columns: 
    - column: Tweet 
    - column: Hashtag 
The table should have the title "TweetHashtags" und the data must be loaded from the server with the following relative URL: 
    "/HashtagService/tweethashtag/hashtag/{id}"

2. The TweetHashtagView must contain the following fields: 
    - name: Hashtag   type: Hashtag 
    - name: Tweet   type: Tweet 
The data source for the [Hashtag] select control should be loaded from the relative URL: 
    "/HashtagService/hashtag"   (HTTP-GET) 
The data source for the [Tweet] select control should be loaded from the relative URL: 
    "/TweetService/tweet"   (HTTP-GET) 
An existing TweetHashtag entity should be loaded from the relative URL: 
    "/HashtagService/tweethashtag/{id}"   (HTTP-GET) 
If a new TweetHashtag entity has been created, the new entity should be posted to the relative URL: 
    "/HashtagService/tweethashtag"   (HTTP-POST) 
If an existing TweetHashtag entity has been updated, the modified entity should be sent to the relative URL: 
    "/HashtagService/tweethashtag/{id}"   (HTTP-PUT) 
If an existing TweetHashtag entity has to be deleted, the following relative URL should be called: 
    "/HashtagService/tweethashtag/{id}"   (HTTP-DELETE)

3. The UserBlockView must contain the following fields: 
    - name: BlockedUser   type: UserAccount 
    - name: CreatedAt   type: STRING 
    - name: User   type: UserAccount 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
The data source for the [BlockedUser] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserBlock entity should be loaded from the relative URL: 
    "/HashtagService/userblock/{id}"   (HTTP-GET) 
If a new UserBlock entity has been created, the new entity should be posted to the relative URL: 
    "/HashtagService/userblock"   (HTTP-POST) 
If an existing UserBlock entity has been updated, the modified entity should be sent to the relative URL: 
    "/HashtagService/userblock/{id}"   (HTTP-PUT) 
If an existing UserBlock entity has to be deleted, the following relative URL should be called: 
    "/HashtagService/userblock/{id}"   (HTTP-DELETE)