Overview
Summary
Contact
Donate
Imprint
Prompt for the
PartnerApp
Please create a React-JS application for the PartnerModule. The application has to offer the following views for the user interface: 1. PartnerView 2. PartnerServiceView 3. PartnerServiceOfferingView 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 PartnerView must contain the following fields: - name: CertificationDate type: DATE - name: Company type: Company - name: Description type: STRING - name: IsCertified type: BOOL - name: PartnerType type: STRING The data source for the [Company] select control should be loaded from the relative URL: "/CompanyService/company" (HTTP-GET) An existing Partner entity should be loaded from the relative URL: "/PartnerService/partner/{id}" (HTTP-GET) If a new Partner entity has been created, the new entity should be posted to the relative URL: "/PartnerService/partner" (HTTP-POST) If an existing Partner entity has been updated, the modified entity should be sent to the relative URL: "/PartnerService/partner/{id}" (HTTP-PUT) If an existing Partner entity has to be deleted, the following relative URL should be called: "/PartnerService/partner/{id}" (HTTP-DELETE) Add a HTML table to the view with the following PartnerServiceOffering columns: - column: Partner - column: PartnerService The table should have the title "PartnerServiceOfferings" und the data must be loaded from the server with the following relative URL: "/PartnerService/partnerserviceoffering/partner/{id}" 2. The PartnerServiceView must contain the following fields: - name: Description type: STRING - name: Name type: STRING An existing PartnerService entity should be loaded from the relative URL: "/PartnerService/partnerservice/{id}" (HTTP-GET) If a new PartnerService entity has been created, the new entity should be posted to the relative URL: "/PartnerService/partnerservice" (HTTP-POST) If an existing PartnerService entity has been updated, the modified entity should be sent to the relative URL: "/PartnerService/partnerservice/{id}" (HTTP-PUT) If an existing PartnerService entity has to be deleted, the following relative URL should be called: "/PartnerService/partnerservice/{id}" (HTTP-DELETE) Add a HTML table to the view with the following PartnerServiceOffering columns: - column: Partner - column: PartnerService The table should have the title "PartnerServiceOfferings" und the data must be loaded from the server with the following relative URL: "/PartnerService/partnerserviceoffering/partnerservice/{id}" 3. The PartnerServiceOfferingView must contain the following fields: - name: Partner type: Partner - name: PartnerService type: PartnerService The data source for the [PartnerService] select control should be loaded from the relative URL: "/PartnerService/partnerservice" (HTTP-GET) The data source for the [Partner] select control should be loaded from the relative URL: "/PartnerService/partner" (HTTP-GET) An existing PartnerServiceOffering entity should be loaded from the relative URL: "/PartnerService/partnerserviceoffering/{id}" (HTTP-GET) If a new PartnerServiceOffering entity has been created, the new entity should be posted to the relative URL: "/PartnerService/partnerserviceoffering" (HTTP-POST) If an existing PartnerServiceOffering entity has been updated, the modified entity should be sent to the relative URL: "/PartnerService/partnerserviceoffering/{id}" (HTTP-PUT) If an existing PartnerServiceOffering entity has to be deleted, the following relative URL should be called: "/PartnerService/partnerserviceoffering/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint