Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum
Prompt for the
MembershipTypeApp
Please create a React-JS application for the MembershipTypeModule. The application has to offer the following views for the user interface: 1. MembershipView 2. MembershipTypeView 3. NewsPostView 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 MembershipView must contain the following fields: - name: AutoRenew type: BOOL - name: CreatedAt type: DATE - name: Customer type: Customer - name: EndDate type: DATE - name: MembershipType type: MembershipType - name: StartDate type: DATE - name: Status type: STRING The data source for the [Customer] select control should be loaded from the relative URL: "/CustomerService/customer" (HTTP-GET) The data source for the [MembershipType] select control should be loaded from the relative URL: "/MembershipTypeService/membershiptype" (HTTP-GET) An existing Membership entity should be loaded from the relative URL: "/MembershipTypeService/membership/{id}" (HTTP-GET) If a new Membership entity has been created, the new entity should be posted to the relative URL: "/MembershipTypeService/membership" (HTTP-POST) If an existing Membership entity has been updated, the modified entity should be sent to the relative URL: "/MembershipTypeService/membership/{id}" (HTTP-PUT) If an existing Membership entity has to be deleted, the following relative URL should be called: "/MembershipTypeService/membership/{id}" (HTTP-DELETE) 2. The MembershipTypeView must contain the following fields: - name: CreatedAt type: DATE - name: Description type: STRING - name: DurationMonths type: LONG - name: IsActive type: BOOL - name: MonthlyFee type: STRING - name: Name type: STRING An existing MembershipType entity should be loaded from the relative URL: "/MembershipTypeService/membershiptype/{id}" (HTTP-GET) If a new MembershipType entity has been created, the new entity should be posted to the relative URL: "/MembershipTypeService/membershiptype" (HTTP-POST) If an existing MembershipType entity has been updated, the modified entity should be sent to the relative URL: "/MembershipTypeService/membershiptype/{id}" (HTTP-PUT) If an existing MembershipType entity has to be deleted, the following relative URL should be called: "/MembershipTypeService/membershiptype/{id}" (HTTP-DELETE) Add a HTML table to the view with the following PriceItem columns: - column: TimeTo - column: Sport - column: PricePerHour - column: BookingType - column: CreatedAt - column: MembershipType - column: DayOfWeek - column: PriceList - column: TimeFrom The table should have the title "PriceItems" und the data must be loaded from the server with the following relative URL: "/PriceListService/priceitem/membershiptype/{id}" Add a HTML table to the view with the following Membership columns: - column: AutoRenew - column: EndDate - column: StartDate - column: CreatedAt - column: MembershipType - column: Customer - column: Status The table should have the title "Memberships" und the data must be loaded from the server with the following relative URL: "/MembershipTypeService/membership/membershiptype/{id}" 3. The NewsPostView must contain the following fields: - name: BodyHtml type: STRING - name: CreatedAt type: DATE - name: Highlighted type: BOOL - name: IsVisible type: BOOL - name: PublishedAt type: DATE - name: Slug type: STRING - name: Title type: STRING An existing NewsPost entity should be loaded from the relative URL: "/MembershipTypeService/newspost/{id}" (HTTP-GET) If a new NewsPost entity has been created, the new entity should be posted to the relative URL: "/MembershipTypeService/newspost" (HTTP-POST) If an existing NewsPost entity has been updated, the modified entity should be sent to the relative URL: "/MembershipTypeService/newspost/{id}" (HTTP-PUT) If an existing NewsPost entity has to be deleted, the following relative URL should be called: "/MembershipTypeService/newspost/{id}" (HTTP-DELETE)
Copy prompt
Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum