Overview
Summary
Contact
Donate
Imprint
Prompt for the
CustomerApp
Please create a React-JS application for the CustomerModule. The application has to offer the following views for the user interface: 1. CustomerView 2. CustomerAddressView 3. LoyaltyCardView 4. LoyaltyProgramView 5. LoyaltyStampView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below. 1. The CustomerView must contain the following fields: - name: CreatedAt type: DATE - name: Email type: STRING - name: FirstName type: STRING - name: IsBlocked type: BOOL - name: LastName type: STRING - name: PhoneNumber type: STRING An existing Customer entity should be loaded from the relative URL: "/CustomerService/customer/{id}" (HTTP-GET) If a new Customer entity has been created, the new entity should be posted to the relative URL: "/CustomerService/customer" (HTTP-POST) If an existing Customer entity has been updated, the modified entity should be sent to the relative URL: "/CustomerService/customer/{id}" (HTTP-PUT) If an existing Customer entity has to be deleted, the following relative URL should be called: "/CustomerService/customer/{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/customer/{id}" Add a HTML table to the view with the following CustomerAddress columns: - column: IsDefault - column: Customer - column: Street - column: AddressExtra - column: Label - column: PostalCode - column: HouseNumber - column: Longitude - column: City - column: Latitude The table should have the title "CustomerAddresss" und the data must be loaded from the server with the following relative URL: "/CustomerService/customeraddress/customer/{id}" Add a HTML table to the view with the following LoyaltyCard columns: - column: CreatedAt - column: LastUpdatedAt - column: Customer - column: IsCompleted - column: CurrentStampCount - column: LoyaltyProgram The table should have the title "LoyaltyCards" und the data must be loaded from the server with the following relative URL: "/CustomerService/loyaltycard/customer/{id}" Add a HTML table to the view with the following Rating columns: - column: CreatedAt - column: Restaurant - column: Comment - column: Customer - column: CustomerOrder - column: IsVerified - column: RatingValue The table should have the title "Ratings" und the data must be loaded from the server with the following relative URL: "/RestaurantTagService/rating/customer/{id}" 2. The CustomerAddressView must contain the following fields: - name: AddressExtra type: STRING - name: City type: City - name: Customer type: Customer - name: HouseNumber type: STRING - name: IsDefault type: BOOL - name: Label type: STRING - name: Latitude type: STRING - name: Longitude type: STRING - name: PostalCode type: STRING - name: Street type: STRING The data source for the [Customer] select control should be loaded from the relative URL: "/CustomerService/customer" (HTTP-GET) The data source for the [City] select control should be loaded from the relative URL: "/RestaurantService/city" (HTTP-GET) An existing CustomerAddress entity should be loaded from the relative URL: "/CustomerService/customeraddress/{id}" (HTTP-GET) If a new CustomerAddress entity has been created, the new entity should be posted to the relative URL: "/CustomerService/customeraddress" (HTTP-POST) If an existing CustomerAddress entity has been updated, the modified entity should be sent to the relative URL: "/CustomerService/customeraddress/{id}" (HTTP-PUT) If an existing CustomerAddress entity has to be deleted, the following relative URL should be called: "/CustomerService/customeraddress/{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/deliveryaddress/{id}" 3. The LoyaltyCardView must contain the following fields: - name: CreatedAt type: DATE - name: CurrentStampCount type: LONG - name: Customer type: Customer - name: IsCompleted type: BOOL - name: LastUpdatedAt type: DATE - name: LoyaltyProgram type: LoyaltyProgram The data source for the [LoyaltyProgram] select control should be loaded from the relative URL: "/CustomerService/loyaltyprogram" (HTTP-GET) The data source for the [Customer] select control should be loaded from the relative URL: "/CustomerService/customer" (HTTP-GET) An existing LoyaltyCard entity should be loaded from the relative URL: "/CustomerService/loyaltycard/{id}" (HTTP-GET) If a new LoyaltyCard entity has been created, the new entity should be posted to the relative URL: "/CustomerService/loyaltycard" (HTTP-POST) If an existing LoyaltyCard entity has been updated, the modified entity should be sent to the relative URL: "/CustomerService/loyaltycard/{id}" (HTTP-PUT) If an existing LoyaltyCard entity has to be deleted, the following relative URL should be called: "/CustomerService/loyaltycard/{id}" (HTTP-DELETE) Add a HTML table to the view with the following LoyaltyStamp columns: - column: OrderAmount - column: StampDateTime - column: LoyaltyCard - column: Notes - column: CustomerOrder The table should have the title "LoyaltyStamps" und the data must be loaded from the server with the following relative URL: "/CustomerService/loyaltystamp/loyaltycard/{id}" 4. The LoyaltyProgramView must contain the following fields: - name: Description type: STRING - name: IsActive type: BOOL - name: Name type: STRING - name: RequiredStamps type: LONG - name: Restaurant type: Restaurant - name: RewardDescription type: STRING The data source for the [Restaurant] select control should be loaded from the relative URL: "/RestaurantService/restaurant" (HTTP-GET) An existing LoyaltyProgram entity should be loaded from the relative URL: "/CustomerService/loyaltyprogram/{id}" (HTTP-GET) If a new LoyaltyProgram entity has been created, the new entity should be posted to the relative URL: "/CustomerService/loyaltyprogram" (HTTP-POST) If an existing LoyaltyProgram entity has been updated, the modified entity should be sent to the relative URL: "/CustomerService/loyaltyprogram/{id}" (HTTP-PUT) If an existing LoyaltyProgram entity has to be deleted, the following relative URL should be called: "/CustomerService/loyaltyprogram/{id}" (HTTP-DELETE) Add a HTML table to the view with the following LoyaltyCard columns: - column: CreatedAt - column: LastUpdatedAt - column: Customer - column: IsCompleted - column: CurrentStampCount - column: LoyaltyProgram The table should have the title "LoyaltyCards" und the data must be loaded from the server with the following relative URL: "/CustomerService/loyaltycard/loyaltyprogram/{id}" 5. The LoyaltyStampView must contain the following fields: - name: CustomerOrder type: LONG - name: LoyaltyCard type: LoyaltyCard - name: Notes type: STRING - name: OrderAmount type: STRING - name: StampDateTime type: DATE The data source for the [LoyaltyCard] select control should be loaded from the relative URL: "/CustomerService/loyaltycard" (HTTP-GET) An existing LoyaltyStamp entity should be loaded from the relative URL: "/CustomerService/loyaltystamp/{id}" (HTTP-GET) If a new LoyaltyStamp entity has been created, the new entity should be posted to the relative URL: "/CustomerService/loyaltystamp" (HTTP-POST) If an existing LoyaltyStamp entity has been updated, the modified entity should be sent to the relative URL: "/CustomerService/loyaltystamp/{id}" (HTTP-PUT) If an existing LoyaltyStamp entity has to be deleted, the following relative URL should be called: "/CustomerService/loyaltystamp/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint