Overview
Summary
Contact
Donate
Imprint
Prompt for the
CampaignApp
Please create a React-JS application for the CampaignModule. The application has to offer the following views for the user interface: 1. AdAccountView 2. CampaignView 3. UserMuteView 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 AdAccountView must contain the following fields: - name: CreatedAt type: STRING - name: Currency type: STRING - name: Name type: STRING - name: OwnerUser type: UserAccount - name: Timezone type: STRING The data source for the [OwnerUser] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) An existing AdAccount entity should be loaded from the relative URL: "/CampaignService/adaccount/{id}" (HTTP-GET) If a new AdAccount entity has been created, the new entity should be posted to the relative URL: "/CampaignService/adaccount" (HTTP-POST) If an existing AdAccount entity has been updated, the modified entity should be sent to the relative URL: "/CampaignService/adaccount/{id}" (HTTP-PUT) If an existing AdAccount entity has to be deleted, the following relative URL should be called: "/CampaignService/adaccount/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Campaign columns: - column: TotalBudget - column: AdAccount - column: EndDate - column: StartDate - column: Status - column: DailyBudget - column: Objective - column: Name The table should have the title "Campaigns" und the data must be loaded from the server with the following relative URL: "/CampaignService/campaign/adaccount/{id}" 2. The CampaignView must contain the following fields: - name: AdAccount type: AdAccount - name: DailyBudget type: DOUBLE - name: EndDate type: STRING - name: Name type: STRING - name: Objective type: STRING - name: StartDate type: STRING - name: Status type: STRING - name: TotalBudget type: DOUBLE The data source for the [AdAccount] select control should be loaded from the relative URL: "/CampaignService/adaccount" (HTTP-GET) An existing Campaign entity should be loaded from the relative URL: "/CampaignService/campaign/{id}" (HTTP-GET) If a new Campaign entity has been created, the new entity should be posted to the relative URL: "/CampaignService/campaign" (HTTP-POST) If an existing Campaign entity has been updated, the modified entity should be sent to the relative URL: "/CampaignService/campaign/{id}" (HTTP-PUT) If an existing Campaign entity has to be deleted, the following relative URL should be called: "/CampaignService/campaign/{id}" (HTTP-DELETE) Add a HTML table to the view with the following PromotedTweet columns: - column: Campaign - column: Tweet - column: Status - column: CreatedAt - column: LineItemName The table should have the title "PromotedTweets" und the data must be loaded from the server with the following relative URL: "/TweetService/promotedtweet/campaign/{id}" 3. The UserMuteView must contain the following fields: - name: CreatedAt type: STRING - name: MutedUser type: UserAccount - name: User type: UserAccount The data source for the [MutedUser] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) The data source for the [User] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) An existing UserMute entity should be loaded from the relative URL: "/CampaignService/usermute/{id}" (HTTP-GET) If a new UserMute entity has been created, the new entity should be posted to the relative URL: "/CampaignService/usermute" (HTTP-POST) If an existing UserMute entity has been updated, the modified entity should be sent to the relative URL: "/CampaignService/usermute/{id}" (HTTP-PUT) If an existing UserMute entity has to be deleted, the following relative URL should be called: "/CampaignService/usermute/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint