Overview
Summary
Contact
Donate
Imprint
Prompt for the
MerchantApp
Please create a React-JS application for the MerchantModule. The application has to offer the following views for the user interface: 1. MerchantView 2. MerchantAddressView 3. MerchantApiCredentialView 4. MerchantBusinessInfoView 5. MerchantWebsiteView 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 MerchantView must contain the following fields: - name: Category type: STRING - name: CreatedAt type: DATE - name: DisplayName type: STRING - name: LegalName type: STRING - name: Status type: STRING - name: UserAccount type: UserAccount - name: WebsiteUrl type: STRING The data source for the [UserAccount] select control should be loaded from the relative URL: "/UserAccountService/useraccount" (HTTP-GET) An existing Merchant entity should be loaded from the relative URL: "/MerchantService/merchant/{id}" (HTTP-GET) If a new Merchant entity has been created, the new entity should be posted to the relative URL: "/MerchantService/merchant" (HTTP-POST) If an existing Merchant entity has been updated, the modified entity should be sent to the relative URL: "/MerchantService/merchant/{id}" (HTTP-PUT) If an existing Merchant entity has to be deleted, the following relative URL should be called: "/MerchantService/merchant/{id}" (HTTP-DELETE) Add a HTML table to the view with the following SubscriptionPlan columns: - column: BillingFrequency - column: Amount - column: Status - column: TrialDays - column: Description - column: Merchant - column: Currency - column: Name - column: BillingInterval The table should have the title "SubscriptionPlans" und the data must be loaded from the server with the following relative URL: "/SubscriptionService/subscriptionplan/merchant/{id}" Add a HTML table to the view with the following Transaction columns: - column: CompletedAt - column: SenderUserAccount - column: ReceiverUserAccount - column: CreatedAt - column: Merchant - column: Status - column: Type - column: NetAmount - column: FundingSource - column: Amount - column: FeeAmount - column: ExternalReference - column: Currency The table should have the title "Transactions" und the data must be loaded from the server with the following relative URL: "/TransactionService/transaction/merchant/{id}" Add a HTML table to the view with the following MerchantBusinessInfo columns: - column: EstablishedAt - column: Merchant - column: RegistrationNumber - column: IndustryCode - column: TaxNumber The table should have the title "MerchantBusinessInfos" und the data must be loaded from the server with the following relative URL: "/MerchantService/merchantbusinessinfo/merchant/{id}" Add a HTML table to the view with the following MerchantApiCredential columns: - column: LastUsedAt - column: Merchant - column: Status - column: CreatedAt - column: ClientSecretHash - column: ClientId The table should have the title "MerchantApiCredentials" und the data must be loaded from the server with the following relative URL: "/MerchantService/merchantapicredential/merchant/{id}" Add a HTML table to the view with the following MerchantAddress columns: - column: PostalCode - column: State - column: AddressType - column: Merchant - column: City - column: Line2 - column: Line1 - column: Country The table should have the title "MerchantAddresss" und the data must be loaded from the server with the following relative URL: "/MerchantService/merchantaddress/merchant/{id}" Add a HTML table to the view with the following Invoice columns: - column: BilledUserAccount - column: IssueDate - column: Transaction - column: Notes - column: TotalAmount - column: DueDate - column: Status - column: Merchant - column: Currency - column: Number The table should have the title "Invoices" und the data must be loaded from the server with the following relative URL: "/CurrencyService/invoice/merchant/{id}" Add a HTML table to the view with the following MerchantWebsite columns: - column: Status - column: Merchant - column: Url - column: VerifiedAt The table should have the title "MerchantWebsites" und the data must be loaded from the server with the following relative URL: "/MerchantService/merchantwebsite/merchant/{id}" Add a HTML table to the view with the following SecurityIncident columns: - column: Severity - column: Description - column: DetectedAt - column: Type - column: ResolvedAt - column: Merchant - column: UserAccount The table should have the title "SecurityIncidents" und the data must be loaded from the server with the following relative URL: "/RegionService/securityincident/merchant/{id}" 2. The MerchantAddressView must contain the following fields: - name: AddressType type: STRING - name: City type: STRING - name: Country type: Country - name: Line1 type: STRING - name: Line2 type: STRING - name: Merchant type: Merchant - name: PostalCode type: STRING - name: State type: STRING The data source for the [Merchant] select control should be loaded from the relative URL: "/MerchantService/merchant" (HTTP-GET) The data source for the [Country] select control should be loaded from the relative URL: "/CountryService/country" (HTTP-GET) An existing MerchantAddress entity should be loaded from the relative URL: "/MerchantService/merchantaddress/{id}" (HTTP-GET) If a new MerchantAddress entity has been created, the new entity should be posted to the relative URL: "/MerchantService/merchantaddress" (HTTP-POST) If an existing MerchantAddress entity has been updated, the modified entity should be sent to the relative URL: "/MerchantService/merchantaddress/{id}" (HTTP-PUT) If an existing MerchantAddress entity has to be deleted, the following relative URL should be called: "/MerchantService/merchantaddress/{id}" (HTTP-DELETE) 3. The MerchantApiCredentialView must contain the following fields: - name: ClientId type: STRING - name: ClientSecretHash type: STRING - name: CreatedAt type: DATE - name: LastUsedAt type: DATE - name: Merchant type: Merchant - name: Status type: STRING The data source for the [Merchant] select control should be loaded from the relative URL: "/MerchantService/merchant" (HTTP-GET) An existing MerchantApiCredential entity should be loaded from the relative URL: "/MerchantService/merchantapicredential/{id}" (HTTP-GET) If a new MerchantApiCredential entity has been created, the new entity should be posted to the relative URL: "/MerchantService/merchantapicredential" (HTTP-POST) If an existing MerchantApiCredential entity has been updated, the modified entity should be sent to the relative URL: "/MerchantService/merchantapicredential/{id}" (HTTP-PUT) If an existing MerchantApiCredential entity has to be deleted, the following relative URL should be called: "/MerchantService/merchantapicredential/{id}" (HTTP-DELETE) 4. The MerchantBusinessInfoView must contain the following fields: - name: EstablishedAt type: DATE - name: IndustryCode type: STRING - name: Merchant type: Merchant - name: RegistrationNumber type: STRING - name: TaxNumber type: STRING The data source for the [Merchant] select control should be loaded from the relative URL: "/MerchantService/merchant" (HTTP-GET) An existing MerchantBusinessInfo entity should be loaded from the relative URL: "/MerchantService/merchantbusinessinfo/{id}" (HTTP-GET) If a new MerchantBusinessInfo entity has been created, the new entity should be posted to the relative URL: "/MerchantService/merchantbusinessinfo" (HTTP-POST) If an existing MerchantBusinessInfo entity has been updated, the modified entity should be sent to the relative URL: "/MerchantService/merchantbusinessinfo/{id}" (HTTP-PUT) If an existing MerchantBusinessInfo entity has to be deleted, the following relative URL should be called: "/MerchantService/merchantbusinessinfo/{id}" (HTTP-DELETE) 5. The MerchantWebsiteView must contain the following fields: - name: Merchant type: Merchant - name: Status type: STRING - name: Url type: STRING - name: VerifiedAt type: DATE The data source for the [Merchant] select control should be loaded from the relative URL: "/MerchantService/merchant" (HTTP-GET) An existing MerchantWebsite entity should be loaded from the relative URL: "/MerchantService/merchantwebsite/{id}" (HTTP-GET) If a new MerchantWebsite entity has been created, the new entity should be posted to the relative URL: "/MerchantService/merchantwebsite" (HTTP-POST) If an existing MerchantWebsite entity has been updated, the modified entity should be sent to the relative URL: "/MerchantService/merchantwebsite/{id}" (HTTP-PUT) If an existing MerchantWebsite entity has to be deleted, the following relative URL should be called: "/MerchantService/merchantwebsite/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint