…o chore/669-update-delegate-card

chore/669-update-delegate-card

Signed-off-by: jankun4 <[email protected]>

In this commit, specific CORS parameters are added to the
`docker-compose.yml.tpl` file to facilitate developers' access to the
metadata validation service from their individual machines within the
dev environment. The CORS configuration includes settings related to
allowed methods, headers, origins, and maximum age. By implementing
these CORS parameters, developers can utilize the metadata validation
service effectively while ensuring secure and controlled access from
their local environments.

The commit makes usage of a variable in the `config.mk` file to
determine the target configuration file dynamically based on the
environment. This change enhances the flexibility and efficiency of the
script, allowing for seamless configuration adjustments across different
environments.

…cy-for-metadata-validation-service-in-dev-environment

[#678] Setting CORS policy for metadata validation service in dev environment

…-ui-tests

[#637] Create atoms components ui tests

fix: fix api connection

…ation-against-cip-fields-to-metadata-validation-service

[#609] feat: add metadata validation against cip fields

Extend the  endpoint by providing both drepHash and drepView, and tx hash of the delegation

Signed-off-by: jankun4 <[email protected]>

Signed-off-by: jankun4 <[email protected]>

…s-displayed-incorrectly

fix/687-voting-power-chip-is-displayed-incorrectly

Implement build process to create images that cannot be pulled from
external repositories when deploying the stack. The modification in the
Makefile sets up the build command to prevent pulling images externally
during the deployment process. By adding the `--build` flag in the
`docker-compose` command, it ensures that images are only built locally
and not fetched from external sources. This aligns with the requirement
to restrict access to the metadata validation service, ensuring that
only localhost is used for accessing resources, thus strengthening
security measures.

In response to the user story requiring the metadata validation service
to be accessible only from localhost for security reasons, this commit
includes a modification to the CSP (Content Security Policy) directive
in the docker-compose.yml file. The change specifically adds
'https://www.googletagmanager.com' to the img-src directive, ensuring
that resources from Google Tag Manager are permitted in the service.
This adjustment enhances security measures by properly configuring the
CSP policy to allow resources only from specified sources.

…adata-validation-service

[#707] Bug in building metadata validation service

…-without-spaces-goes-beyond-card

[#699] GA - card - very long title without spaces goes beyond card

…-lists-and-pending-transactions-on-drep-explorer

feat/681-add-loaders-to-the-lists-and-pending-transactions-on-drep-explorer

Signed-off-by: jankun4 <[email protected]>

…names

The commit adjusts the names of the routers in the Traefik configuration
within the docker-compose.yml file. This modification ensures that the
routers are distinctively named and do not share names with the
services, enhancing clarity and manageability of the setup. By renaming
the router identifiers, it becomes easier to differentiate them from the
corresponding services, thus facilitating maintenance and
troubleshooting of the configuration.

The adjustments in this commit focus on correcting the indentation in
the Traefik configuration section within the docker-compose.yml.tpl
file. The changes entail ensuring consistent and proper alignment of the
services' definitions, specifically the metadata-validation service, to
enhance readability and maintainability. By reformatting the
indentation, the Traefik configuration becomes more organized,
facilitating easier navigation and understanding of the setup.

The commit modifies the Traefik image version specified in the
docker-compose.yml.tpl file from v2.10 to v3.0. By updating the Traefik
image, we ensure compatibility with the necessary features and
improvements introduced in version 3.0. This adjustment aligns with the
user story's goal to enhance load balancing and routing setup in the dev
environment by making sure that the configuration utilizes the latest
Traefik version for more efficient backend service management and
testing capabilities.

The commit enhances the routing setup in the Traefik configuration
within the docker-compose.yml.tpl file by implementing better
priorities. By adjusting the priority of the router for the frontend
service to 1, the routing for this service looses precedence, ensuring
that frontend traffic is correctly directed. This change aims to
optimize the routing logic, ensuring that the frontend service receives
appropriate traffic allocation and improving the overall efficiency of
the load balancing and routing setup in the dev environment.

This is an actual fix of the problem stated in the related issue.

…d balancer

The commit enhances the Traefik configuration within the
docker-compose.yml.tpl file by adding healthcheck configurations to the
two primary backend services, `metadata-validation` and `backend`. These
healthchecks include defining paths, ports, intervals, and timeouts for
monitoring the health and status of the backend services. By
implementing healthchecks, Traefik can periodically verify the
availability and responsiveness of the backend services through
specified endpoints, contributing to improved load balancing and routing
efficiency. This change directly addresses the user story requirement to
ensure the backend service is correctly defined, reachable, and
functioning optimally in the dev environment for effective testing and
debugging purposes.

The changes made in this commit focus on enhancing the CORS
configuration for the dev environment by adding an additional exception
to allow specific origins. The modification includes appending
"http://localhost:5173" to the list of allowed hosts when the
environment is set to "dev." This adjustment aims to address
Cross-Origin Resource Sharing (CORS) issues related to accessing
services from different origins, ensuring that the specified host is
permitted to interact with the backend service seamlessly.

…n-doesnt-finish-80-chars-long-title-not-cut-not-submittitng

[#655] fix: fix DRep registration when the DRep name is longer

…d-balancing-and-routing-issue

[#715] Dev environment load balancing and routing issue

…on test

…ls-to-not-block-signing-transactions-with-metadata

[#710] fix displaying modals to not block signing transactions

…n-due-to-fetching-the-resource-blocked-by-csp

[#712] fix: Fix displaying Governance Actions that fails the validation test

[#651] fix: correct text of governance action type

Signed-off-by: jankun4 <[email protected]>

…ckend-to-drep-list

[#723] Apply business logic to drep list

…search-functionality

[#674] GA Search - Voted on - Add search functionality

…opening-usersnap-feedback-widget-on-the-custom-buttons

chore/546-handle-action-of-opening-usersnap-feedback-widget-on-the-custom-buttons

…-to-review-the-submitted-transaction

chore/573-link-to-cexplorer-to-review-the-submitted-transaction

…m Item details

Add allure reporting support in backend test

The Cardano infrastructure on SanchoNet required an update to the
Cardano DB Sync element. By changing the image tag from "sancho-4.1.0"
to "sancho-4.2.0" in the Makefile, the DB sync component was effectively
updated to the new version. This modification ensures that the network
remains up-to-date and functions properly.

Add allure-report generation for playwright tests

…arting-cardano-infrastructure-on-sanchonet

[#714] Updating and restarting Cardano infrastructure on SanchoNet

…ow object

…next-to-the-ga-type-already-assigned

feat/464-missing-info-icon-next-to-the-ga-type-already-assigned

fix/drep-directory

…ar useges

[#509 #752] Wallet transaction errors modals

…-sort-order-and-filtering-is-not-kept-after-back-from-item-details-planned-to-next-iter

[#604] GA Display: search, sort and filter is not kept after Back fro…