Fix/wallet text

[ananyayaya129]

Description of change

changed text as per the request and fixed styling on pages with useless scroll

Issue Number

Type of change

• Update (a change which updates existing functionality)
• Fix (a change which fixes an issue)

How the change has been tested

Locally Tested

Change checklist

• I have ensured that the CI Checks pass locally
• I have removed any unnecessary logic
• My code is well documented
• I have signed my commits
• My code follows the pattern of the application
• I have self reviewed my code

Summary by CodeRabbit

• New Features

  • Introduced webhook integration and mapping logic for data synchronization between platforms (Blabsy and Pictique).
  • Added support for eVault data storage and mapping in the web3-adapter.
  • Implemented Firestore and database watchers for real-time data updates.

• Improvements

  • Enhanced onboarding, registration, and login flows in the eID Wallet app.
  • Refined UI and layout across multiple components for better usability and consistency.
  • Updated environment, build, and branding configurations for several platforms.

• Bug Fixes

  • Improved error handling and access control logic in backend services.
  • Addressed issues with authentication state management and profile data fetching.

• Chores

  • Updated and added new dependencies to support GraphQL, web3, and testing.
  • Reformatted code for consistency and maintainability.

• Documentation

  • Added localization and mapping configuration files for easier setup and internationalization.

• Tests

  • Removed outdated or redundant test files in preparation for new architecture.

• Refactor

  • Replaced and consolidated mapping, webhook, and data transformation logic for streamlined cross-platform data handling.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This update introduces a comprehensive overhaul of the web3 adapter infrastructure, adds new mapping and database modules, and integrates enhanced eVault and webhook functionality across Pictique and Blabsy platforms. It also features UI and UX refinements for eID Wallet and Pictique, updates dependencies, and introduces new event-driven mechanisms and type definitions.

Changes

File(s) / Group	Change Summary
infrastructure/eid-wallet/*	UI/UX refinements, branding updates, layout adjustments, subtitle rendering improvements, onboarding flow enhancements, and new dependencies.
infrastructure/evault-core/src/db/db.service.ts, .../retry-neo4j.ts, .../protocol/graphql-server.ts, ...	Introduced updateMetaEnvelopeById method, Neo4j retry logic, GraphQL mutation for updating meta envelopes, and related schema updates.
infrastructure/evault-core/src/evault.ts	Refactored EVault class with static create() method and improved Neo4j connection handling.
infrastructure/evault-core/src/protocol/vault-access-guard.ts	Simplified access control logic to always allow access.
infrastructure/evault-core/src/protocol/examples/examples.ts	Added example for new update mutation.
infrastructure/web3-adapter/*	Major refactor: removed old adapter/tests, added new mapping/db modules, introduced Web3Adapter and EVaultClient classes, new mapping types, updated tsconfig, and dependencies.
platforms/blabsy-w3ds-auth-api/*	Added webhook controller, initialized web3 adapter, updated dependencies, and introduced Firestore watcher and mapping files.
platforms/blabsy/*	Updated environment variables, UI text, modal dialogs, and menu positioning.
platforms/metagram/project.inlang/*	Added Inlang localization configuration and project metadata.
platforms/pictique-api/*	Integrated new webhook controller, mapping files, event emitter, message service, and entity subscriber; refactored services and controllers; added migration for ID mapping table.
platforms/pictique/*	UI/UX improvements, updated state management, profile and post handling, and utility enhancements for authentication and API usage.

Sequence Diagram(s)

Web3 Adapter Data Flow

sequenceDiagram
    participant Platform as Platform (Pictique/Blabsy)
    participant Web3Adapter
    participant MappingDB
    participant EVaultClient
    participant eVault

    Platform->>Web3Adapter: handleChange({data, tableName, participants})
    Web3Adapter->>MappingDB: storeMapping(localId, globalId, tableName)
    Web3Adapter->>EVaultClient: storeMetaEnvelope(metaEnvelope)
    EVaultClient->>eVault: GraphQL mutation (store/update envelope)
    eVault-->>EVaultClient: Envelope ID / Result
    EVaultClient-->>Web3Adapter: Envelope ID / Result
    Web3Adapter-->>Platform: Success/Failure

Loading

Webhook Handling Flow

sequenceDiagram
    participant ExternalPlatform
    participant WebhookController
    participant Web3Adapter
    participant PlatformDB

    ExternalPlatform->>WebhookController: POST /api/webhook (data)
    WebhookController->>Web3Adapter: handleChange({data, tableName, ...})
    Web3Adapter->>PlatformDB: Update/Create entity
    PlatformDB-->>Web3Adapter: Result
    Web3Adapter-->>WebhookController: Status
    WebhookController-->>ExternalPlatform: Response

Loading

Possibly related PRs

• #115: Both PRs focus on enhancing the web3 adapter, including mapping, data transformation, and eVault integration.
• #229: Both PRs involve changes to user authentication, profile data handling, and integration with blockchain-based services.
• #179: Both PRs relate to infrastructure and deployment changes for eVault and its integration with wallet applications.

Poem

(\(\
( -.-)
o_(")(")

A hop, a leap, across the code,
The web3 bridge is now bestowed!
With mappings neat and data tight,
Envelopes travel left and right.
Platforms chat, their data flows—
A rabbit’s dream: it simply grows!
🥕✨

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.