58 Open Issues Need Help Last updated: Jul 1, 2026

Open Issues Need Help

View All on GitHub
enhancement good first issue frontend feature priority: low Website Page
bug good first issue frontend UI/UX priority: medium Website Page
enhancement good first issue frontend priority: high
bug good first issue UI/UX priority: medium functional
bug good first issue priority: high
bug good first issue frontend verification required

AI Summary: The website experiences multiple React hydration mismatches on initial load, where the server-rendered HTML differs from the client-side React output. This results in console warnings across various components, indicating inconsistent rendering between server-side and client-side processes. It's classified as a minor severity issue.

Complexity: 3/5
bug good first issue frontend
good first issue frontend priority: high refactoring
enhancement good first issue frontend UI/UX
enhancement good first issue frontend UI/UX
enhancement good first issue frontend UI/UX
bug good first issue

AI Summary: Write unit tests for the NextLink component to improve its test coverage. The goal is to address the currently low test coverage shown in the provided screenshot.

Complexity: 2/5
good first issue frontend feature

AI Summary: Write unit tests for the `useScrollDirection` hook in the `app/shared/hooks/use-scroll-direction/useScrollDirection.ts` file to increase test coverage to 80% or more. The provided image shows the current test coverage and the failing path.

Complexity: 3/5
good first issue frontend test

AI Summary: Write unit tests for the `Header.tsx` component located in the `app/shared/components/Header` directory to increase the overall test coverage to at least 80%. The provided screenshot shows the current test coverage and the failing path.

Complexity: 3/5
good first issue frontend test

AI Summary: Write a unit test for a ThemeProvider component in a React application. The test should verify that the provider renders children correctly, that child components can access theme values, and that custom theme overrides are applied correctly. The test should achieve at least 80% test coverage.

Complexity: 3/5
good first issue

AI Summary: Increase the test coverage of the Music Search component to above 3%. This involves writing additional unit tests to cover currently untested functions and edge cases within the component. Before starting, verify that the Music Search component has been merged into the `develop` branch.

Complexity: 3/5
good first issue

AI Summary: Fix a bug in the '/artistry' page where the 'open opus row' icon is not visible until the row is opened. The issue is a visual discrepancy; the icon should be visible even when the row is closed. The fix involves adjusting the UI to display the icon correctly in its closed state.

Complexity: 2/5
bug good first issue frontend

AI Summary: Fix a bug in the translation of the 'Переглянути ноти' button on the /artistry page. The button should correctly reflect the selected language (English or Ukrainian). This involves investigating the translation mechanism within the application's codebase and correcting the logic to ensure proper language switching.

Complexity: 3/5
bug good first issue frontend

AI Summary: Improve the test coverage of the Slider component to meet the project's minimum threshold (e.g., 66%) by adding or modifying unit tests to cover conditional branches currently not evaluated. This involves analyzing the existing code, identifying gaps in test coverage, and writing new tests to address those gaps.

Complexity: 3/5
good first issue

AI Summary: Fix the responsiveness of SVGs in the footer. The SVGs should stop scaling beyond a width of 1728px to prevent text overflow and maintain consistent sizing.

Complexity: 2/5
bug good first issue frontend