Overview
Summary
Contact
Donate
Imprint
Prompt for the
ApiClientApp
Please create a React-JS application for the ApiClientModule. The application has to offer the following views for the user interface: 1. ApiClientView 2. ApiUsageLogView 3. VesselTechnicalDetailView 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 ApiClientView must contain the following fields: - name: ClientKey type: STRING - name: ClientName type: STRING - name: ClientSecretHash type: STRING - name: CreatedUtc type: DATE - name: IsActive type: BOOL - name: UserAccount type: UserAccount The data source for the [UserAccount] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) An existing ApiClient entity should be loaded from the relative URL: "/ApiClientService/apiclient/{id}" (HTTP-GET) If a new ApiClient entity has been created, the new entity should be posted to the relative URL: "/ApiClientService/apiclient" (HTTP-POST) If an existing ApiClient entity has been updated, the modified entity should be sent to the relative URL: "/ApiClientService/apiclient/{id}" (HTTP-PUT) If an existing ApiClient entity has to be deleted, the following relative URL should be called: "/ApiClientService/apiclient/{id}" (HTTP-DELETE) Add a HTML table to the view with the following ApiUsageLog columns: - column: ApiClient - column: ResponseStatusCode - column: RequestTimestampUtc - column: BytesSent - column: BytesReceived - column: Endpoint The table should have the title "ApiUsageLogs" und the data must be loaded from the server with the following relative URL: "/ApiClientService/apiusagelog/apiclient/{id}" 2. The ApiUsageLogView must contain the following fields: - name: ApiClient type: ApiClient - name: BytesReceived type: LONG - name: BytesSent type: LONG - name: Endpoint type: STRING - name: RequestTimestampUtc type: DATE - name: ResponseStatusCode type: LONG The data source for the [ApiClient] select control should be loaded from the relative URL: "/ApiClientService/apiclient" (HTTP-GET) An existing ApiUsageLog entity should be loaded from the relative URL: "/ApiClientService/apiusagelog/{id}" (HTTP-GET) If a new ApiUsageLog entity has been created, the new entity should be posted to the relative URL: "/ApiClientService/apiusagelog" (HTTP-POST) If an existing ApiUsageLog entity has been updated, the modified entity should be sent to the relative URL: "/ApiClientService/apiusagelog/{id}" (HTTP-PUT) If an existing ApiUsageLog entity has to be deleted, the following relative URL should be called: "/ApiClientService/apiusagelog/{id}" (HTTP-DELETE) 3. The VesselTechnicalDetailView must contain the following fields: - name: Builder type: STRING - name: EnginePowerKw type: STRING - name: EngineType type: STRING - name: HullType type: STRING - name: IceClass type: STRING - name: ManagerName type: STRING - name: MaxSpeed type: STRING - name: OwnerName type: STRING - name: ServiceSpeed type: STRING - name: Vessel type: Vessel The data source for the [Vessel] select control should be loaded from the relative URL: "/VesselService/vessel" (HTTP-GET) An existing VesselTechnicalDetail entity should be loaded from the relative URL: "/ApiClientService/vesseltechnicaldetail/{id}" (HTTP-GET) If a new VesselTechnicalDetail entity has been created, the new entity should be posted to the relative URL: "/ApiClientService/vesseltechnicaldetail" (HTTP-POST) If an existing VesselTechnicalDetail entity has been updated, the modified entity should be sent to the relative URL: "/ApiClientService/vesseltechnicaldetail/{id}" (HTTP-PUT) If an existing VesselTechnicalDetail entity has to be deleted, the following relative URL should be called: "/ApiClientService/vesseltechnicaldetail/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint