Overview
Summary
Contact
Donate
Imprint
Prompt for the
PlaylistApp
Please create a React-JS application for the PlaylistModule. The application has to offer the following views for the user interface: 1. AcquisitionView 2. CreatorToolView 3. PlaylistView 4. PlaylistItemView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below. 1. The AcquisitionView must contain the following fields: - name: Acquirer type: LONG - name: AnnouncedOn type: DATE - name: ClosedOn type: DATE - name: Description type: STRING - name: IntegratedInto type: LONG - name: PriceEur type: DOUBLE - name: TargetCountry type: LONG - name: TargetName type: STRING An existing Acquisition entity should be loaded from the relative URL: "/PlaylistService/acquisition/{id}" (HTTP-GET) If a new Acquisition entity has been created, the new entity should be posted to the relative URL: "/PlaylistService/acquisition" (HTTP-POST) If an existing Acquisition entity has been updated, the modified entity should be sent to the relative URL: "/PlaylistService/acquisition/{id}" (HTTP-PUT) If an existing Acquisition entity has to be deleted, the following relative URL should be called: "/PlaylistService/acquisition/{id}" (HTTP-DELETE) 2. The CreatorToolView must contain the following fields: - name: Description type: STRING - name: IsOwnedBySpotify type: BOOL - name: Name type: STRING An existing CreatorTool entity should be loaded from the relative URL: "/PlaylistService/creatortool/{id}" (HTTP-GET) If a new CreatorTool entity has been created, the new entity should be posted to the relative URL: "/PlaylistService/creatortool" (HTTP-POST) If an existing CreatorTool entity has been updated, the modified entity should be sent to the relative URL: "/PlaylistService/creatortool/{id}" (HTTP-PUT) If an existing CreatorTool entity has to be deleted, the following relative URL should be called: "/PlaylistService/creatortool/{id}" (HTTP-DELETE) Add a HTML table to the view with the following CreatorToolUsage columns: - column: Podcast - column: Artist - column: UserAccount - column: StartedAt - column: CreatorTool The table should have the title "CreatorToolUsages" und the data must be loaded from the server with the following relative URL: "/TrackService/creatortoolusage/creatortool/{id}" 3. The PlaylistView must contain the following fields: - name: CreatedAt type: DATE - name: Description type: STRING - name: IsAlgorithmic type: BOOL - name: IsCollaborative type: BOOL - name: IsEditorial type: BOOL - name: OwnerUser type: LONG - name: Title type: STRING An existing Playlist entity should be loaded from the relative URL: "/PlaylistService/playlist/{id}" (HTTP-GET) If a new Playlist entity has been created, the new entity should be posted to the relative URL: "/PlaylistService/playlist" (HTTP-POST) If an existing Playlist entity has been updated, the modified entity should be sent to the relative URL: "/PlaylistService/playlist/{id}" (HTTP-PUT) If an existing Playlist entity has to be deleted, the following relative URL should be called: "/PlaylistService/playlist/{id}" (HTTP-DELETE) Add a HTML table to the view with the following PlaylistItem columns: - column: AddedAt - column: Track - column: AddedByUser - column: PodcastEpisode - column: Playlist - column: SortOrder The table should have the title "PlaylistItems" und the data must be loaded from the server with the following relative URL: "/PlaylistService/playlistitem/playlist/{id}" 4. The PlaylistItemView must contain the following fields: - name: AddedAt type: DATE - name: AddedByUser type: LONG - name: Playlist type: Playlist - name: PodcastEpisode type: PodcastEpisode - name: SortOrder type: LONG - name: Track type: Track The data source for the [Playlist] select control should be loaded from the relative URL: "/PlaylistService/playlist" (HTTP-GET) The data source for the [Track] select control should be loaded from the relative URL: "/TrackService/track" (HTTP-GET) The data source for the [PodcastEpisode] select control should be loaded from the relative URL: "/TrackService/podcastepisode" (HTTP-GET) An existing PlaylistItem entity should be loaded from the relative URL: "/PlaylistService/playlistitem/{id}" (HTTP-GET) If a new PlaylistItem entity has been created, the new entity should be posted to the relative URL: "/PlaylistService/playlistitem" (HTTP-POST) If an existing PlaylistItem entity has been updated, the modified entity should be sent to the relative URL: "/PlaylistService/playlistitem/{id}" (HTTP-PUT) If an existing PlaylistItem entity has to be deleted, the following relative URL should be called: "/PlaylistService/playlistitem/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint