Overview
Summary
Contact
Donate
Imprint
Prompt for the
PersonApp
Please create a React-JS application for the PersonModule. The application has to offer the following views for the user interface: 1. ContentDealTitleView 2. ContentPersonCreditView 3. PersonView 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 ContentDealTitleView must contain the following fields: - name: ContentDeal type: ContentDeal - name: ContentTitle type: ContentTitle - name: Notes type: STRING The data source for the [ContentDeal] select control should be loaded from the relative URL: "/CompanyService/contentdeal" (HTTP-GET) The data source for the [ContentTitle] select control should be loaded from the relative URL: "/ContentTitleService/contenttitle" (HTTP-GET) An existing ContentDealTitle entity should be loaded from the relative URL: "/PersonService/contentdealtitle/{id}" (HTTP-GET) If a new ContentDealTitle entity has been created, the new entity should be posted to the relative URL: "/PersonService/contentdealtitle" (HTTP-POST) If an existing ContentDealTitle entity has been updated, the modified entity should be sent to the relative URL: "/PersonService/contentdealtitle/{id}" (HTTP-PUT) If an existing ContentDealTitle entity has to be deleted, the following relative URL should be called: "/PersonService/contentdealtitle/{id}" (HTTP-DELETE) 2. The ContentPersonCreditView must contain the following fields: - name: CharacterName type: STRING - name: ContentTitle type: ContentTitle - name: CreditType type: STRING - name: Person type: Person The data source for the [Person] select control should be loaded from the relative URL: "/PersonService/person" (HTTP-GET) The data source for the [ContentTitle] select control should be loaded from the relative URL: "/ContentTitleService/contenttitle" (HTTP-GET) An existing ContentPersonCredit entity should be loaded from the relative URL: "/PersonService/contentpersoncredit/{id}" (HTTP-GET) If a new ContentPersonCredit entity has been created, the new entity should be posted to the relative URL: "/PersonService/contentpersoncredit" (HTTP-POST) If an existing ContentPersonCredit entity has been updated, the modified entity should be sent to the relative URL: "/PersonService/contentpersoncredit/{id}" (HTTP-PUT) If an existing ContentPersonCredit entity has to be deleted, the following relative URL should be called: "/PersonService/contentpersoncredit/{id}" (HTTP-DELETE) 3. The PersonView must contain the following fields: - name: Biography type: STRING - name: BirthDate type: DATE - name: FirstName type: STRING - name: FullName type: STRING - name: LastName type: STRING An existing Person entity should be loaded from the relative URL: "/PersonService/person/{id}" (HTTP-GET) If a new Person entity has been created, the new entity should be posted to the relative URL: "/PersonService/person" (HTTP-POST) If an existing Person entity has been updated, the modified entity should be sent to the relative URL: "/PersonService/person/{id}" (HTTP-PUT) If an existing Person entity has to be deleted, the following relative URL should be called: "/PersonService/person/{id}" (HTTP-DELETE) Add a HTML table to the view with the following ContentPersonCredit columns: - column: ContentTitle - column: CharacterName - column: CreditType - column: Person The table should have the title "ContentPersonCredits" und the data must be loaded from the server with the following relative URL: "/PersonService/contentpersoncredit/person/{id}" Add a HTML table to the view with the following PersonRole columns: - column: EndDate - column: Person - column: StartDate - column: Company - column: RoleName The table should have the title "PersonRoles" und the data must be loaded from the server with the following relative URL: "/CompanyService/personrole/person/{id}"
Copy prompt
Overview
Summary
Contact
Donate
Imprint