Prompt for the PaymentMethodApp

Please create a React-JS application for the PaymentMethodModule. The application  has to offer the following views for the user interface: 
    1. CustomerOrderView 
    2. PaymentMethodView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 2 views are defined below.

1. The CustomerOrderView must contain the following fields: 
    - name: Customer   type: Customer 
    - name: DeliveryAddress   type: CustomerAddress 
    - name: DeliveryFee   type: STRING 
    - name: DiscountAmount   type: STRING 
    - name: LoyaltyCard   type: LONG 
    - name: Notes   type: STRING 
    - name: OrderDateTime   type: DATE 
    - name: OrderNumber   type: STRING 
    - name: OrderType   type: STRING 
    - name: PaymentFee   type: STRING 
    - name: PaymentMethod   type: PaymentMethod 
    - name: Restaurant   type: Restaurant 
    - name: ScheduledDateTime   type: DATE 
    - name: Status   type: STRING 
    - name: SubtotalAmount   type: STRING 
    - name: TotalAmount   type: STRING 
The data source for the [Restaurant] select control should be loaded from the relative URL: 
    "/RestaurantService/restaurant"   (HTTP-GET) 
The data source for the [Customer] select control should be loaded from the relative URL: 
    "/CustomerService/customer"   (HTTP-GET) 
The data source for the [DeliveryAddress] select control should be loaded from the relative URL: 
    "/CustomerService/customeraddress"   (HTTP-GET) 
The data source for the [PaymentMethod] select control should be loaded from the relative URL: 
    "/PaymentMethodService/paymentmethod"   (HTTP-GET) 
An existing CustomerOrder entity should be loaded from the relative URL: 
    "/PaymentMethodService/customerorder/{id}"   (HTTP-GET) 
If a new CustomerOrder entity has been created, the new entity should be posted to the relative URL: 
    "/PaymentMethodService/customerorder"   (HTTP-POST) 
If an existing CustomerOrder entity has been updated, the modified entity should be sent to the relative URL: 
    "/PaymentMethodService/customerorder/{id}"   (HTTP-PUT) 
If an existing CustomerOrder entity has to be deleted, the following relative URL should be called: 
    "/PaymentMethodService/customerorder/{id}"   (HTTP-DELETE)

2. The PaymentMethodView must contain the following fields: 
    - name: Description   type: STRING 
    - name: IsActive   type: BOOL 
    - name: IsOnline   type: BOOL 
    - name: Name   type: STRING 
An existing PaymentMethod entity should be loaded from the relative URL: 
    "/PaymentMethodService/paymentmethod/{id}"   (HTTP-GET) 
If a new PaymentMethod entity has been created, the new entity should be posted to the relative URL: 
    "/PaymentMethodService/paymentmethod"   (HTTP-POST) 
If an existing PaymentMethod entity has been updated, the modified entity should be sent to the relative URL: 
    "/PaymentMethodService/paymentmethod/{id}"   (HTTP-PUT) 
If an existing PaymentMethod entity has to be deleted, the following relative URL should be called: 
    "/PaymentMethodService/paymentmethod/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following CustomerOrder columns: 
    - column: Notes 
    - column: DeliveryAddress 
    - column: Customer 
    - column: PaymentFee 
    - column: OrderNumber 
    - column: OrderType 
    - column: PaymentMethod 
    - column: TotalAmount 
    - column: Restaurant 
    - column: LoyaltyCard 
    - column: DeliveryFee 
    - column: OrderDateTime 
    - column: SubtotalAmount 
    - column: ScheduledDateTime 
    - column: DiscountAmount 
    - column: Status 
The table should have the title "CustomerOrders" und the data must be loaded from the server with the following relative URL: 
    "/PaymentMethodService/customerorder/paymentmethod/{id}"

Overview

Summary

Contact

Donate

Imprint