Overview
Summary
Contact
Donate
Imprint
Prompt for the
StockListingApp
Please create a React-JS application for the StockListingModule. The application has to offer the following views for the user interface: 1. IndexMembershipView 2. PromotionView 3. StockListingView 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 IndexMembershipView must contain the following fields: - name: EndDate type: DATE - name: IndexName type: STRING - name: StartDate type: DATE - name: StockListing type: StockListing The data source for the [StockListing] select control should be loaded from the relative URL: "/StockListingService/stocklisting" (HTTP-GET) An existing IndexMembership entity should be loaded from the relative URL: "/StockListingService/indexmembership/{id}" (HTTP-GET) If a new IndexMembership entity has been created, the new entity should be posted to the relative URL: "/StockListingService/indexmembership" (HTTP-POST) If an existing IndexMembership entity has been updated, the modified entity should be sent to the relative URL: "/StockListingService/indexmembership/{id}" (HTTP-PUT) If an existing IndexMembership entity has to be deleted, the following relative URL should be called: "/StockListingService/indexmembership/{id}" (HTTP-DELETE) 2. The PromotionView must contain the following fields: - name: Code type: STRING - name: Currency type: STRING - name: Description type: STRING - name: DiscountType type: STRING - name: DiscountValue type: DOUBLE - name: EndDate type: DATE - name: MaxRedemptions type: INT - name: StartDate type: DATE An existing Promotion entity should be loaded from the relative URL: "/StockListingService/promotion/{id}" (HTTP-GET) If a new Promotion entity has been created, the new entity should be posted to the relative URL: "/StockListingService/promotion" (HTTP-POST) If an existing Promotion entity has been updated, the modified entity should be sent to the relative URL: "/StockListingService/promotion/{id}" (HTTP-PUT) If an existing Promotion entity has to be deleted, the following relative URL should be called: "/StockListingService/promotion/{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/promotion/{id}" 3. The StockListingView must contain the following fields: - name: Company type: Company - name: DelistingDate type: DATE - name: Exchange type: STRING - name: ListingDate type: DATE - name: Notes type: STRING - name: Ticker type: STRING The data source for the [Company] select control should be loaded from the relative URL: "/CompanyService/company" (HTTP-GET) An existing StockListing entity should be loaded from the relative URL: "/StockListingService/stocklisting/{id}" (HTTP-GET) If a new StockListing entity has been created, the new entity should be posted to the relative URL: "/StockListingService/stocklisting" (HTTP-POST) If an existing StockListing entity has been updated, the modified entity should be sent to the relative URL: "/StockListingService/stocklisting/{id}" (HTTP-PUT) If an existing StockListing entity has to be deleted, the following relative URL should be called: "/StockListingService/stocklisting/{id}" (HTTP-DELETE) Add a HTML table to the view with the following IndexMembership columns: - column: StockListing - column: StartDate - column: EndDate - column: IndexName The table should have the title "IndexMemberships" und the data must be loaded from the server with the following relative URL: "/StockListingService/indexmembership/stocklisting/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint