Open Issues Need Help
View All on GitHubAI Summary: Implement a header and footer for a Spotify web application. The header should conditionally render content based on user login status (logged in or logged out). The footer should include application links. Both header and footer must match a provided Figma design.
AI Summary: Test the Spotify OAuth 2.0 flow for a full-stack application. This involves verifying the user login process, token storage in a MongoDB database, and redirection to the application's search page. The test should confirm successful authorization, token persistence with timestamp, and proper redirection based on authentication status (new user vs. returning user).
AI Summary: Implement environment variable checks in the client-side application to differentiate between development and production environments. This involves adding environment variables for dev and prod configurations and incorporating conditional logic to use the appropriate settings based on the environment. The task references a previous assignment (DWA deployment to Heroku) as a potential guide.
AI Summary: Add a logo.ico file to the `<head>` section of the client's index.html file to set the page title icon. This involves locating or creating a suitable .ico file and adding a `<link>` tag within the `<head>` of the index.html file, referencing the path to the .ico file.
AI Summary: The task involves reviewing a peer's Spotify application project (including a demonstration video and code on GitHub) and providing constructive feedback according to specified guidelines. This feedback should address code quality, functionality, and overall project progress.
AI Summary: The task involves reviewing a peer's Spotify web application project (including a demonstration video and code on GitHub) and providing constructive feedback according to specified guidelines. This feedback should address code quality, functionality, and overall project progress.
AI Summary: The task involves reviewing a peer's Spotify web application project (including a demonstration video and code on GitHub) and providing constructive feedback according to specified guidelines. This feedback should address code quality, functionality, and overall project progress.
AI Summary: This task requires setting up and configuring a MongoDB database to persist JWT tokens after user authentication within a Spotify application. This involves establishing a connection to the MongoDB database, defining a schema for storing user data (including JWT tokens and expiration dates), and implementing the necessary logic in the server-side code to save and retrieve JWT tokens securely.
AI Summary: The task involves reviewing the Spotify authentication workflow documentation, including the overview, getting started guide, tutorials, how-to's, and reference materials on albums, artists, search, and tracks. This is to aid in the completion of a Spotify web application project that uses the Spotify Web API for searching and displaying artist, album, and track information.
AI Summary: Review a peer's Spotify web application project (code and video presentation) and provide constructive feedback based on provided guidelines. This involves assessing code quality, functionality, and presentation clarity, then offering suggestions for improvement.
AI Summary: Deploy a Spotify API application to Heroku. This involves ensuring basic API endpoints are functional, setting up a MongoDB Atlas database, and then deploying the application to Heroku. The application allows users to search for artists, albums, and tracks using the Spotify Web API.
AI Summary: Build a full-stack Spotify application using Node.js, Express, MongoDB, and React (or similar frontend framework). The application should allow users to search for artists, albums, and tracks via the Spotify API, displaying results and linking to the Spotify player. JWT authentication is required. The design is flexible, but must meet all endpoint requirements (Artist, Album, Track).
AI Summary: Set up a development environment for a Spotify web application backend. This involves installing Node.js, Express.js, and MongoDB, configuring environment variables (including a Spotify API key), and ensuring the backend server runs correctly. The setup includes creating a `.env` file with database connection details and API keys.
AI Summary: Set up a Git repository with an Agile workflow, including a main branch, a development branch, milestones, issues, and Kanboard integration for a Spotify web application project. This involves creating the branches, defining milestones and issues, and configuring Kanboard to track progress.
AI Summary: Attend a weekly SCRUM meeting for Milestone 2 of a Spotify application development project. The project involves building a full-stack application using Node.js, Express, MongoDB, and the Spotify Web API, requiring JWT authentication and handling user data. The meeting is scheduled for Wednesdays at 3:00 PM.
AI Summary: Attend a weekly SCRUM meeting for Milestone 3 of a Spotify application development project. The project involves building a full-stack application using Node.js, Express, MongoDB, and the Spotify Web API, requiring JWT authentication and handling user data. The meeting is scheduled for Wednesdays at 3:00 PM.
AI Summary: Attend a weekly SCRUM meeting for Milestone 4 of a Spotify application development project. The project involves building a full-stack application using Node.js, Express, MongoDB, and the Spotify Web API, requiring JWT authentication and handling user data. The meeting is scheduled for Wednesdays at 3:00 PM.
AI Summary: Create a README.md file documenting a Spotify web application built using Node.js, Express, MongoDB, and the Spotify Web API. The README should include sections on project overview, prerequisites (software and versions), getting started instructions (including setup, installation, and running the application), and relevant links (server and client URLs, API endpoints).
AI Summary: This task involves creating a Spotify web application using Node.js, Express, MongoDB, and the Spotify Web API. The application allows users to search for artists, albums, and tracks, and redirects them to the Spotify player. The student must also create weekly progress videos and provide constructive feedback on a peer's project, following specific guidelines.
AI Summary: This task requires a weekly progress check-in, addressing any questions or concerns about the Spotify application project. If no questions exist, a summary of the week's tasks for building the full-stack application (including front-end and back-end development, API integration with Spotify, and database management) should be provided.
AI Summary: Complete the front-end user interface (UI) for a Spotify application. This involves implementing the remaining UI elements based on pre-existing designs or provided specifications. The application already has a functional back-end, including user authentication and Spotify API integration.
AI Summary: Implement logic to redirect users to the login page if a valid JWT token is not found. This involves checking the token status on each request and conditionally rendering the login page or the main application based on the result. The existing login functionality should be integrated with this token check.
AI Summary: The task requires building a user interface (UI) login screen for a Spotify application. This screen should facilitate user authorization with their Spotify account, obtaining a JWT (JSON Web Token) upon successful authentication. The JWT will then be used for subsequent API calls within the application.
AI Summary: This task involves creating a Spotify web application using Node.js, Express, MongoDB, and the Spotify Web API. The application allows users to search for artists, albums, and tracks, and redirects them to the Spotify player. The student must also create weekly progress videos and provide constructive feedback on a peer's project, following specific guidelines.
AI Summary: This task requires a weekly progress check-in for a Spotify application project. If there are no questions, a summary of the week's tasks for building a full-stack Spotify application (using Node.js, Express, MongoDB, and React) should be provided. The application allows users to search for artists, albums, and tracks via the Spotify API and requires JWT authentication.
AI Summary: This task requires a weekly progress check-in, addressing any questions or concerns about the Spotify application project. If no questions exist, a summary of the week's tasks for building the full-stack application (including front-end and back-end development, API integration with Spotify, and database management) should be provided.
AI Summary: Implement a route or middleware function to check the validity of a JWT (JSON Web Token) stored in a MongoDB database. This function should determine if a user's Spotify account needs re-authorization by checking the JWT's status (e.g., expiration date, token revocation). The function should return a boolean value indicating whether the user needs to log in and re-authorize their Spotify account.
AI Summary: Implement a JWT refresh token mechanism for the Spotify application. This involves integrating Spotify's refresh token functionality into the existing authentication flow to allow users to automatically refresh their expired JWTs without requiring re-authentication, ensuring continuous access to the Spotify API.
AI Summary: Define custom backend API routes for a Spotify application using Node.js, Express, and MongoDB. The routes should handle user authentication (using JWT), and provide endpoints to interact with the Spotify API for searching and retrieving artist, album, and track information. Existing user management endpoints are already in place.
AI Summary: This task involves creating a Spotify web application using Node.js, Express, MongoDB, and the Spotify Web API. The application allows users to search for artists, albums, and tracks, and redirects them to the Spotify player. The student must also create weekly progress videos and provide constructive feedback on a peer's project, following specific guidelines.
AI Summary: Implement the backend routes for a Spotify application, following the Spotify authentication code flow documented at https://developer.spotify.com/documentation/general/guides/authorization/code-flow/. This involves creating routes for user management (GET, POST, PUT, DELETE) and Spotify API interaction (artist, album, track searches). The backend uses Node.js, Express, Mongoose, and MongoDB.
AI Summary: Create a Spotify OAuth application through the Spotify developer portal, obtain the Client ID and Client Secret, and integrate these credentials into the provided Node.js/Express/MongoDB application using environment variables. This involves setting up the OAuth flow to allow users to securely connect their Spotify accounts to the application.
AI Summary: This task involves setting up a Spotify developer account to obtain an API key, which is necessary to build a Spotify web application. This includes agreeing to Spotify's terms of service and following their getting started guide to generate the API key. The key is then used within a Node.js/Express/MongoDB application to access the Spotify Web API for searching artists, albums, and tracks.
AI Summary: Develop a backend API for a Spotify application using Node.js, Express.js, Mongoose, and MongoDB. The API should handle user authentication (using JWT), manage user data, and interact with the Spotify Web API to retrieve artist, album, and track information. Environment variables will be loaded from a .env file.
AI Summary: The task requires creating a Spotify Developer account to obtain an API key, which is then integrated into a full-stack Spotify application. This involves setting up the application's backend (Node.js, Express, MongoDB) and frontend, handling user authentication and authorization via JWT, and making API calls to the Spotify Web API to search for and display artist, album, and track information.
AI Summary: This task involves building a Spotify web application using Node.js, Express, MongoDB, and the Spotify Web API. The project requires creating both a server and client-side application, handling user authentication with JWT, and implementing search functionality for artists, albums, and tracks. Additionally, weekly progress updates (videos and code reviews) must be submitted and peer feedback provided, following specific guidelines.