Overview
Summary
Contact
Donate
Imprint
Prompt for the
VehicleApp
Please create a React-JS application for the VehicleModule. The application has to offer the following views for the user interface: 1. DriverAccountView 2. DriverVehicleView 3. TripView 4. TripPaymentView 5. TripPromotionView 6. VehicleView 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 DriverAccountView must contain the following fields: - name: BackgroundCheckStatus type: STRING - name: DeactivationDate type: DATE - name: LicenseCountry type: STRING - name: LicenseNumber type: STRING - name: OnboardingDate type: DATE - name: PlatformUser type: PlatformUser - name: Rating type: DOUBLE - name: VehicleRegistrationCountry type: STRING The data source for the [PlatformUser] select control should be loaded from the relative URL: "/PlatformUserService/platformuser" (HTTP-GET) An existing DriverAccount entity should be loaded from the relative URL: "/VehicleService/driveraccount/{id}" (HTTP-GET) If a new DriverAccount entity has been created, the new entity should be posted to the relative URL: "/VehicleService/driveraccount" (HTTP-POST) If an existing DriverAccount entity has been updated, the modified entity should be sent to the relative URL: "/VehicleService/driveraccount/{id}" (HTTP-PUT) If an existing DriverAccount entity has to be deleted, the following relative URL should be called: "/VehicleService/driveraccount/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Trip columns: - column: CompletedAt - column: RequestedAt - column: PriceCurrency - column: Service - column: StartedAt - column: AcceptedAt - column: DurationMinutes - column: DriverAccount - column: Status - column: DistanceKm - column: PriceAmount - column: RiderAccount - column: OriginCity - column: Vehicle - column: CanceledAt - column: DestinationCity The table should have the title "Trips" und the data must be loaded from the server with the following relative URL: "/VehicleService/trip/driveraccount/{id}" Add a HTML table to the view with the following DriverVehicle columns: - column: EndDate - column: StartDate - column: DriverAccount - column: PrimaryFlag - column: Vehicle The table should have the title "DriverVehicles" und the data must be loaded from the server with the following relative URL: "/VehicleService/drivervehicle/driveraccount/{id}" 2. The DriverVehicleView must contain the following fields: - name: DriverAccount type: DriverAccount - name: EndDate type: DATE - name: PrimaryFlag type: BOOL - name: StartDate type: DATE - name: Vehicle type: Vehicle The data source for the [Vehicle] select control should be loaded from the relative URL: "/VehicleService/vehicle" (HTTP-GET) The data source for the [DriverAccount] select control should be loaded from the relative URL: "/VehicleService/driveraccount" (HTTP-GET) An existing DriverVehicle entity should be loaded from the relative URL: "/VehicleService/drivervehicle/{id}" (HTTP-GET) If a new DriverVehicle entity has been created, the new entity should be posted to the relative URL: "/VehicleService/drivervehicle" (HTTP-POST) If an existing DriverVehicle entity has been updated, the modified entity should be sent to the relative URL: "/VehicleService/drivervehicle/{id}" (HTTP-PUT) If an existing DriverVehicle entity has to be deleted, the following relative URL should be called: "/VehicleService/drivervehicle/{id}" (HTTP-DELETE) 3. The TripView must contain the following fields: - name: AcceptedAt type: STRING - name: CanceledAt type: STRING - name: CompletedAt type: STRING - name: DestinationCity type: City - name: DistanceKm type: DOUBLE - name: DriverAccount type: DriverAccount - name: DurationMinutes type: INT - name: OriginCity type: City - name: PriceAmount type: DOUBLE - name: PriceCurrency type: STRING - name: RequestedAt type: STRING - name: RiderAccount type: RiderAccount - name: Service type: Service - name: StartedAt type: STRING - name: Status type: STRING - name: Vehicle type: Vehicle The data source for the [Vehicle] select control should be loaded from the relative URL: "/VehicleService/vehicle" (HTTP-GET) The data source for the [DestinationCity] select control should be loaded from the relative URL: "/CityService/city" (HTTP-GET) The data source for the [RiderAccount] select control should be loaded from the relative URL: "/PlatformUserService/rideraccount" (HTTP-GET) The data source for the [DriverAccount] select control should be loaded from the relative URL: "/VehicleService/driveraccount" (HTTP-GET) The data source for the [Service] select control should be loaded from the relative URL: "/CompanyService/service" (HTTP-GET) The data source for the [OriginCity] select control should be loaded from the relative URL: "/CityService/city" (HTTP-GET) An existing Trip entity should be loaded from the relative URL: "/VehicleService/trip/{id}" (HTTP-GET) If a new Trip entity has been created, the new entity should be posted to the relative URL: "/VehicleService/trip" (HTTP-POST) If an existing Trip entity has been updated, the modified entity should be sent to the relative URL: "/VehicleService/trip/{id}" (HTTP-PUT) If an existing Trip entity has to be deleted, the following relative URL should be called: "/VehicleService/trip/{id}" (HTTP-DELETE) Add a HTML table to the view with the following TripPromotion columns: - column: AppliedAmount - column: Currency - column: Trip - column: Promotion The table should have the title "TripPromotions" und the data must be loaded from the server with the following relative URL: "/VehicleService/trippromotion/trip/{id}" Add a HTML table to the view with the following TripPayment columns: - column: Amount - column: RefundAmount - column: RefundCurrency - column: Currency - column: CapturedAt - column: Trip - column: PaymentMethod The table should have the title "TripPayments" und the data must be loaded from the server with the following relative URL: "/VehicleService/trippayment/trip/{id}" 4. The TripPaymentView must contain the following fields: - name: Amount type: DOUBLE - name: CapturedAt type: STRING - name: Currency type: STRING - name: PaymentMethod type: PaymentMethod - name: RefundAmount type: DOUBLE - name: RefundCurrency type: STRING - name: Trip type: Trip The data source for the [Trip] select control should be loaded from the relative URL: "/VehicleService/trip" (HTTP-GET) The data source for the [PaymentMethod] select control should be loaded from the relative URL: "/PlatformUserService/paymentmethod" (HTTP-GET) An existing TripPayment entity should be loaded from the relative URL: "/VehicleService/trippayment/{id}" (HTTP-GET) If a new TripPayment entity has been created, the new entity should be posted to the relative URL: "/VehicleService/trippayment" (HTTP-POST) If an existing TripPayment entity has been updated, the modified entity should be sent to the relative URL: "/VehicleService/trippayment/{id}" (HTTP-PUT) If an existing TripPayment entity has to be deleted, the following relative URL should be called: "/VehicleService/trippayment/{id}" (HTTP-DELETE) 5. The TripPromotionView must contain the following fields: - name: AppliedAmount type: DOUBLE - name: Currency type: STRING - name: Promotion type: Promotion - name: Trip type: Trip The data source for the [Trip] select control should be loaded from the relative URL: "/VehicleService/trip" (HTTP-GET) The data source for the [Promotion] select control should be loaded from the relative URL: "/StockListingService/promotion" (HTTP-GET) An existing TripPromotion entity should be loaded from the relative URL: "/VehicleService/trippromotion/{id}" (HTTP-GET) If a new TripPromotion entity has been created, the new entity should be posted to the relative URL: "/VehicleService/trippromotion" (HTTP-POST) If an existing TripPromotion entity has been updated, the modified entity should be sent to the relative URL: "/VehicleService/trippromotion/{id}" (HTTP-PUT) If an existing TripPromotion entity has to be deleted, the following relative URL should be called: "/VehicleService/trippromotion/{id}" (HTTP-DELETE) 6. The VehicleView must contain the following fields: - name: Capacity type: INT - name: Color type: STRING - name: Make type: STRING - name: Model type: STRING - name: PlateCountry type: STRING - name: PlateNumber type: STRING - name: VehicleType type: STRING - name: Year type: INT An existing Vehicle entity should be loaded from the relative URL: "/VehicleService/vehicle/{id}" (HTTP-GET) If a new Vehicle entity has been created, the new entity should be posted to the relative URL: "/VehicleService/vehicle" (HTTP-POST) If an existing Vehicle entity has been updated, the modified entity should be sent to the relative URL: "/VehicleService/vehicle/{id}" (HTTP-PUT) If an existing Vehicle entity has to be deleted, the following relative URL should be called: "/VehicleService/vehicle/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Trip columns: - column: CompletedAt - column: RequestedAt - column: PriceCurrency - column: Service - column: StartedAt - column: AcceptedAt - column: DurationMinutes - column: DriverAccount - column: Status - column: DistanceKm - column: PriceAmount - column: RiderAccount - column: OriginCity - column: Vehicle - column: CanceledAt - column: DestinationCity The table should have the title "Trips" und the data must be loaded from the server with the following relative URL: "/VehicleService/trip/vehicle/{id}" Add a HTML table to the view with the following DriverVehicle columns: - column: EndDate - column: StartDate - column: DriverAccount - column: PrimaryFlag - column: Vehicle The table should have the title "DriverVehicles" und the data must be loaded from the server with the following relative URL: "/VehicleService/drivervehicle/vehicle/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint