awesome-repositories.com
Blog
MCP
awesome-repositories.com

Descoperă cele mai bune repository-uri open source cu căutare AI.

ExploreazăCăutări recomandateAlternative open-sourceSoftware self-hostedBlogHartă site
ProiectServer MCPDespreCum realizăm clasamentulPresă
LegalConfidențialitateTermeni
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

3 repository-uri

Awesome GitHub RepositoriesState Validation

Verification of entity states to ensure expected values exist before executing logic.

Distinct from Entity State Management: Focuses on validating the presence and correctness of a state to prevent errors, rather than just representing the state.

Explore 3 awesome GitHub repositories matching web development · State Validation. Refine with filters or upvote what's useful.

Awesome State Validation GitHub Repositories

Găsește cele mai bune repo-uri cu AI.Vom căuta cele mai potrivite repository-uri folosind AI.
  • threedotslabs/wild-workouts-go-ddd-exampleAvatar ThreeDotsLabs

    ThreeDotsLabs/wild-workouts-go-ddd-example

    6,348Vezi pe GitHub↗

    This project is a reference implementation of Domain-Driven Design, Clean Architecture, and Command Query Responsibility Segregation (CQRS) patterns using the Go programming language. It serves as a sample application to demonstrate how to decouple core domain rules from infrastructure and delivery mechanisms. The system is built as a gRPC microservices architecture, utilizing type-safe communication and service contracts. It implements an event-driven architecture to manage eventual consistency and asynchronous processing, specifically employing the Outbox pattern to ensure reliable messagin

    Prevents invalid object states by restricting updates to a public API of behavior-oriented methods.

    Goclean-architecturecqrsddd
    Vezi pe GitHub↗6,348
  • effector/effectorAvatar effector

    effector/effector

    4,837Vezi pe GitHub↗

    Effector is a reactive state management library designed for building complex, event-driven applications. It functions as a data flow engine that models application logic as a directed acyclic graph, ensuring that state updates propagate automatically through interconnected nodes. By utilizing atomic state updates and declarative unit composition, the library maintains data consistency and provides a predictable execution model for managing application state. The project distinguishes itself through its framework-agnostic architecture, which decouples business logic from user interface implem

    Verifies if a value is a specific state management primitive to ensure type safety during runtime.

    TypeScriptbusiness-logiceffectorevent-driven
    Vezi pe GitHub↗4,837
  • zerobias/effectorAvatar zerobias

    zerobias/effector

    4,837Vezi pe GitHub↗

    Effector is a reactive state management library and data flow orchestrator designed for building complex, event-driven applications. It models application logic as a directed acyclic graph, where state updates and asynchronous side effects propagate automatically through declarative pipelines. By decoupling business logic from user interface layers, it allows developers to maintain state in independent containers that communicate via standard interfaces, ensuring the system remains framework-agnostic. The library distinguishes itself through its robust support for isolated execution scopes, w

    Determines whether a provided value is a valid state management unit such as a store, event, effect, domain, or scope.

    TypeScript
    Vezi pe GitHub↗4,837
  1. Home
  2. Web Development
  3. Frontend Development Tools
  4. State & Data Management
  5. Data Synchronization Primitives
  6. Entity State Management
  7. State Validation

Explorează sub-etichetele

  • DomainEnforcement of valid object states by restricting updates to a public API of behavior-oriented methods. **Distinct from State Validation:** Focuses on business entity state validity via encapsulation, not generic data validation or ledger agreement.
  • Unit Type ValidatorsUtilities for determining if a value is a valid state management unit like a store, event, or effect. **Distinct from State Validation:** Distinct from State Validation: focuses on validating the type/identity of the unit itself rather than the correctness of its state value.