Overview
Summary
Contact
Donate
Imprint
Prompt for the
SubscriptionPlanApp
Please create a React-JS application for the SubscriptionPlanModule. The application has to offer the following views for the user interface: 1. PlanFeatureView 2. SubscriptionFeatureView 3. SubscriptionPlanView 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 PlanFeatureView must contain the following fields: - name: IsIncluded type: BOOL - name: SubscriptionFeature type: SubscriptionFeature - name: SubscriptionPlan type: SubscriptionPlan The data source for the [SubscriptionPlan] select control should be loaded from the relative URL: "/SubscriptionPlanService/subscriptionplan" (HTTP-GET) The data source for the [SubscriptionFeature] select control should be loaded from the relative URL: "/SubscriptionPlanService/subscriptionfeature" (HTTP-GET) An existing PlanFeature entity should be loaded from the relative URL: "/SubscriptionPlanService/planfeature/{id}" (HTTP-GET) If a new PlanFeature entity has been created, the new entity should be posted to the relative URL: "/SubscriptionPlanService/planfeature" (HTTP-POST) If an existing PlanFeature entity has been updated, the modified entity should be sent to the relative URL: "/SubscriptionPlanService/planfeature/{id}" (HTTP-PUT) If an existing PlanFeature entity has to be deleted, the following relative URL should be called: "/SubscriptionPlanService/planfeature/{id}" (HTTP-DELETE) 2. The SubscriptionFeatureView must contain the following fields: - name: Description type: STRING - name: Name type: STRING An existing SubscriptionFeature entity should be loaded from the relative URL: "/SubscriptionPlanService/subscriptionfeature/{id}" (HTTP-GET) If a new SubscriptionFeature entity has been created, the new entity should be posted to the relative URL: "/SubscriptionPlanService/subscriptionfeature" (HTTP-POST) If an existing SubscriptionFeature entity has been updated, the modified entity should be sent to the relative URL: "/SubscriptionPlanService/subscriptionfeature/{id}" (HTTP-PUT) If an existing SubscriptionFeature entity has to be deleted, the following relative URL should be called: "/SubscriptionPlanService/subscriptionfeature/{id}" (HTTP-DELETE) Add a HTML table to the view with the following PlanFeature columns: - column: IsIncluded - column: SubscriptionPlan - column: SubscriptionFeature The table should have the title "PlanFeatures" und the data must be loaded from the server with the following relative URL: "/SubscriptionPlanService/planfeature/subscriptionfeature/{id}" 3. The SubscriptionPlanView must contain the following fields: - name: Description type: STRING - name: IsDuo type: BOOL - name: IsFamily type: BOOL - name: IsMini type: BOOL - name: IsPaid type: BOOL - name: IsStudent type: BOOL - name: MaxBitrateKbps type: LONG - name: MaxDevices type: LONG - name: MaxOfflineTracks type: LONG - name: Name type: STRING An existing SubscriptionPlan entity should be loaded from the relative URL: "/SubscriptionPlanService/subscriptionplan/{id}" (HTTP-GET) If a new SubscriptionPlan entity has been created, the new entity should be posted to the relative URL: "/SubscriptionPlanService/subscriptionplan" (HTTP-POST) If an existing SubscriptionPlan entity has been updated, the modified entity should be sent to the relative URL: "/SubscriptionPlanService/subscriptionplan/{id}" (HTTP-PUT) If an existing SubscriptionPlan entity has to be deleted, the following relative URL should be called: "/SubscriptionPlanService/subscriptionplan/{id}" (HTTP-DELETE) Add a HTML table to the view with the following StreamEvent columns: - column: Track - column: PodcastEpisode - column: SubscriptionPlan - column: StartedAt - column: Country - column: IsCountedForRoyalty - column: UserAccount - column: DurationSeconds The table should have the title "StreamEvents" und the data must be loaded from the server with the following relative URL: "/TrackService/streamevent/subscriptionplan/{id}" Add a HTML table to the view with the following PlanFeature columns: - column: IsIncluded - column: SubscriptionPlan - column: SubscriptionFeature The table should have the title "PlanFeatures" und the data must be loaded from the server with the following relative URL: "/SubscriptionPlanService/planfeature/subscriptionplan/{id}" Add a HTML table to the view with the following UserSubscription columns: - column: HouseholdAddress - column: IsPrimaryHolder - column: SubscriptionPlan - column: StartedAt - column: UserAccount - column: EndedAt - column: IsAutoRenew The table should have the title "UserSubscriptions" und the data must be loaded from the server with the following relative URL: "/UserAccountService/usersubscription/subscriptionplan/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint