FinesseStudioLab/Trivela

AI Summary: This issue proposes adding a global error boundary component to the React application. The goal is to gracefully handle rendering errors by displaying a user-friendly message and providing options to retry the action or navigate to the homepage.

AI Summary: This issue requests the implementation of a dark mode toggle for the application. Users should be able to switch between light and dark themes, and their preference should be saved using localStorage. The theme change should be applied via CSS variables or by toggling a class on the body element.

AI Summary: This issue proposes adding fundamental accessibility features to the project. It specifically calls for the implementation of semantic HTML, the use of ARIA labels where appropriate, the addition of visible focus styles, and ensuring that the primary user flows are navigable using only a keyboard.

AI Summary: This issue requests the implementation of visual feedback for campaign list loading. It requires displaying a loading spinner while data is being fetched and an error message if the request fails. The campaign list itself should be hidden or disabled until the data is successfully loaded.

AI Summary: This issue requests the addition of unit tests for the campaign CRUD (Create, Read, Update, Delete) operations. The tests should specifically cover status codes, the shape of the responses, and handling of 404 errors when a campaign ID is not found.

AI Summary: This issue proposes adding a new API endpoint, GET /api/config, to the Soroban RPC. This endpoint will expose public configuration details like the RPC URL, Stellar network, and optional contract IDs, providing a single source of truth for the frontend.

AI Summary: This issue proposes adding middleware to a backend application to log key details of incoming requests. The logged information should include the HTTP method, requested path, response status code, and the time taken to process the request. The suggestion is to use existing libraries like `morgan` for this purpose.

AI Summary: This issue requests the addition of a new query parameter, `?active=true|false`, to the existing `GET /api/campaigns` endpoint. The goal is to filter the returned list of campaigns based on their active status.

AI Summary: This issue requests the addition of a new section to the project's README file. This section should detail the exact commands and environment variables needed to build and deploy Soroban contracts, specifically `stellar contract build` and `stellar contract deploy`.

AI Summary: This issue requests the addition of new unit tests for a campaign smart contract. Specifically, it aims to verify that the `set_active` function can only be called by an administrator, that registration is only permitted when the campaign is inactive, and that the `is_participant` function correctly handles unknown addresses.

AI Summary: This issue requests the addition of unit tests for specific edge cases within a rewards smart contract. The tests should cover scenarios like claiming more than the available balance, credit overflow, attempting to register twice in a campaign, and accessing uninitialized contract states.

AI Summary: This issue proposes adding a `metadata()` view function to the rewards contract. This function should return the contract's name and an optional symbol/decimals, primarily for frontend consumption. The goal is to make essential contract information easily accessible.

AI Summary: This issue requests the addition of Soroban events to the rewards contract for `credit` and `claim` operations. These events should log relevant information such as the user and the amount involved. The event details should also be documented in the contract's README or inline comments.