Overview
Summary
Contact
Donate
Imprint
Prompt for the
UserAccountApp
Please create a React-JS application for the UserAccountModule. The application has to offer the following views for the user interface: 1. FeedbackView 2. OrderEntityView 3. OrderItemView 4. PaymentView 5. ShippingDetailView 6. UserAccountView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 6 views are defined below. 1. The FeedbackView must contain the following fields: - name: Comment type: STRING - name: FeedbackDate type: DATE - name: FromUserAccount type: UserAccount - name: OrderItem type: OrderItem - name: Rating type: LONG - name: ToUserAccount type: UserAccount The data source for the [ToUserAccount] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) The data source for the [OrderItem] select control should be loaded from the relative URL: "/UserAccountService/orderitem" (HTTP-GET) The data source for the [FromUserAccount] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) An existing Feedback entity should be loaded from the relative URL: "/UserAccountService/feedback/{id}" (HTTP-GET) If a new Feedback entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/feedback" (HTTP-POST) If an existing Feedback entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/feedback/{id}" (HTTP-PUT) If an existing Feedback entity has to be deleted, the following relative URL should be called: "/UserAccountService/feedback/{id}" (HTTP-DELETE) 2. The OrderEntityView must contain the following fields: - name: BuyerUserAccount type: UserAccount - name: Currency type: STRING - name: OrderDate type: DATE - name: SourceChannel type: STRING - name: Status type: STRING - name: TotalAmount type: STRING The data source for the [BuyerUserAccount] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) An existing OrderEntity entity should be loaded from the relative URL: "/UserAccountService/orderentity/{id}" (HTTP-GET) If a new OrderEntity entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/orderentity" (HTTP-POST) If an existing OrderEntity entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/orderentity/{id}" (HTTP-PUT) If an existing OrderEntity entity has to be deleted, the following relative URL should be called: "/UserAccountService/orderentity/{id}" (HTTP-DELETE) Add a HTML table to the view with the following OrderItem columns: - column: Quantity - column: Currency - column: SellerUserAccount - column: FulfillmentStatus - column: UnitPrice - column: Listing - column: OrderEntity The table should have the title "OrderItems" und the data must be loaded from the server with the following relative URL: "/UserAccountService/orderitem/orderentity/{id}" Add a HTML table to the view with the following Payment columns: - column: PaymentDate - column: PaymentProvider - column: Currency - column: Status - column: OrderEntity - column: Amount - column: TransactionReference The table should have the title "Payments" und the data must be loaded from the server with the following relative URL: "/UserAccountService/payment/orderentity/{id}" 3. The OrderItemView must contain the following fields: - name: Currency type: STRING - name: FulfillmentStatus type: STRING - name: Listing type: Listing - name: OrderEntity type: OrderEntity - name: Quantity type: LONG - name: SellerUserAccount type: UserAccount - name: UnitPrice type: STRING The data source for the [OrderEntity] select control should be loaded from the relative URL: "/UserAccountService/orderentity" (HTTP-GET) The data source for the [Listing] select control should be loaded from the relative URL: "/ListingService/listing" (HTTP-GET) The data source for the [SellerUserAccount] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) An existing OrderItem entity should be loaded from the relative URL: "/UserAccountService/orderitem/{id}" (HTTP-GET) If a new OrderItem entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/orderitem" (HTTP-POST) If an existing OrderItem entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/orderitem/{id}" (HTTP-PUT) If an existing OrderItem entity has to be deleted, the following relative URL should be called: "/UserAccountService/orderitem/{id}" (HTTP-DELETE) Add a HTML table to the view with the following ShippingDetail columns: - column: ServiceLevel - column: Carrier - column: ActualDeliveryDate - column: ShippingCost - column: TrackingNumber - column: EstimatedDeliveryDate - column: Currency - column: OrderItem - column: ShipDate The table should have the title "ShippingDetails" und the data must be loaded from the server with the following relative URL: "/UserAccountService/shippingdetail/orderitem/{id}" Add a HTML table to the view with the following Dispute columns: - column: DisputeType - column: OpenedByUserAccount - column: CloseDate - column: Resolution - column: OpenDate - column: OrderItem - column: Description - column: Status The table should have the title "Disputes" und the data must be loaded from the server with the following relative URL: "/DisputeService/dispute/orderitem/{id}" Add a HTML table to the view with the following Feedback columns: - column: ToUserAccount - column: Comment - column: FeedbackDate - column: Rating - column: FromUserAccount - column: OrderItem The table should have the title "Feedbacks" und the data must be loaded from the server with the following relative URL: "/UserAccountService/feedback/orderitem/{id}" 4. The PaymentView must contain the following fields: - name: Amount type: STRING - name: Currency type: STRING - name: OrderEntity type: OrderEntity - name: PaymentDate type: DATE - name: PaymentProvider type: STRING - name: Status type: STRING - name: TransactionReference type: STRING The data source for the [OrderEntity] select control should be loaded from the relative URL: "/UserAccountService/orderentity" (HTTP-GET) An existing Payment entity should be loaded from the relative URL: "/UserAccountService/payment/{id}" (HTTP-GET) If a new Payment entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/payment" (HTTP-POST) If an existing Payment entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/payment/{id}" (HTTP-PUT) If an existing Payment entity has to be deleted, the following relative URL should be called: "/UserAccountService/payment/{id}" (HTTP-DELETE) 5. The ShippingDetailView must contain the following fields: - name: ActualDeliveryDate type: DATE - name: Carrier type: STRING - name: Currency type: STRING - name: EstimatedDeliveryDate type: DATE - name: OrderItem type: OrderItem - name: ServiceLevel type: STRING - name: ShipDate type: DATE - name: ShippingCost type: STRING - name: TrackingNumber type: STRING The data source for the [OrderItem] select control should be loaded from the relative URL: "/UserAccountService/orderitem" (HTTP-GET) An existing ShippingDetail entity should be loaded from the relative URL: "/UserAccountService/shippingdetail/{id}" (HTTP-GET) If a new ShippingDetail entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/shippingdetail" (HTTP-POST) If an existing ShippingDetail entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/shippingdetail/{id}" (HTTP-PUT) If an existing ShippingDetail entity has to be deleted, the following relative URL should be called: "/UserAccountService/shippingdetail/{id}" (HTTP-DELETE) 6. The UserAccountView must contain the following fields: - name: Country type: STRING - name: Email type: STRING - name: IsBusiness type: BOOL - name: RegistrationDate type: DATE - name: Status type: STRING - name: Username type: STRING An existing UserAccount entity should be loaded from the relative URL: "/UserAccountService/useraccount/{id}" (HTTP-GET) If a new UserAccount entity has been created, the new entity should be posted to the relative URL: "/UserAccountService/useraccount" (HTTP-POST) If an existing UserAccount entity has been updated, the modified entity should be sent to the relative URL: "/UserAccountService/useraccount/{id}" (HTTP-PUT) If an existing UserAccount entity has to be deleted, the following relative URL should be called: "/UserAccountService/useraccount/{id}" (HTTP-DELETE) Add a HTML table to the view with the following FraudCase columns: - column: CloseDate - column: Description - column: Dispute - column: Outcome - column: RelatedUserAccount - column: OpenDate - column: CaseType The table should have the title "FraudCases" und the data must be loaded from the server with the following relative URL: "/DisputeService/fraudcase/relateduseraccount/{id}" Add a HTML table to the view with the following FixedPriceOffer columns: - column: BuyerUserAccount - column: OfferDate - column: Currency - column: Listing - column: Status - column: OfferedPrice The table should have the title "FixedPriceOffers" und the data must be loaded from the server with the following relative URL: "/ListingService/fixedpriceoffer/buyeruseraccount/{id}" Add a HTML table to the view with the following OrderItem columns: - column: Quantity - column: Currency - column: SellerUserAccount - column: FulfillmentStatus - column: UnitPrice - column: Listing - column: OrderEntity The table should have the title "OrderItems" und the data must be loaded from the server with the following relative URL: "/UserAccountService/orderitem/selleruseraccount/{id}" Add a HTML table to the view with the following Dispute columns: - column: DisputeType - column: OpenedByUserAccount - column: CloseDate - column: Resolution - column: OpenDate - column: OrderItem - column: Description - column: Status The table should have the title "Disputes" und the data must be loaded from the server with the following relative URL: "/DisputeService/dispute/openedbyuseraccount/{id}" Add a HTML table to the view with the following Bid columns: - column: BidAmount - column: Auction - column: Currency - column: BidTime - column: IsWinning - column: BidderUserAccount The table should have the title "Bids" und the data must be loaded from the server with the following relative URL: "/AuctionService/bid/bidderuseraccount/{id}" Add a HTML table to the view with the following Feedback columns: - column: ToUserAccount - column: Comment - column: FeedbackDate - column: Rating - column: FromUserAccount - column: OrderItem The table should have the title "Feedbacks" und the data must be loaded from the server with the following relative URL: "/UserAccountService/feedback/fromuseraccount/{id}" Add a HTML table to the view with the following Feedback columns: - column: ToUserAccount - column: Comment - column: FeedbackDate - column: Rating - column: FromUserAccount - column: OrderItem The table should have the title "Feedbacks" und the data must be loaded from the server with the following relative URL: "/UserAccountService/feedback/touseraccount/{id}" Add a HTML table to the view with the following DeveloperApplication columns: - column: Status - column: Name - column: ApiKey - column: OwnerUserAccount - column: CreatedDate The table should have the title "DeveloperApplications" und the data must be loaded from the server with the following relative URL: "/UserRoleService/developerapplication/owneruseraccount/{id}" Add a HTML table to the view with the following UserAccountRole columns: - column: UserAccount - column: AssignedDate - column: UserRole The table should have the title "UserAccountRoles" und the data must be loaded from the server with the following relative URL: "/UserRoleService/useraccountrole/useraccount/{id}" Add a HTML table to the view with the following Listing columns: - column: BuyNowPrice - column: ListingType - column: StartPrice - column: SellerUserAccount - column: LocationCountry - column: Category - column: QuantityAvailable - column: Currency - column: StartDate - column: EndDate - column: Status - column: Title - column: Description - column: LocationRegion The table should have the title "Listings" und the data must be loaded from the server with the following relative URL: "/ListingService/listing/selleruseraccount/{id}" Add a HTML table to the view with the following OrderEntity columns: - column: OrderDate - column: BuyerUserAccount - column: Currency - column: TotalAmount - column: SourceChannel - column: Status The table should have the title "OrderEntitys" und the data must be loaded from the server with the following relative URL: "/UserAccountService/orderentity/buyeruseraccount/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint