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

Découvrez les meilleurs dépôts open-source grâce à notre recherche par IA.

ExplorerRecherches sélectionnéesAlternatives open sourceLogiciels auto-hébergésBlogPlan du site
ProjetServeur MCPÀ proposNotre méthodologiePresse
Mentions légalesConfidentialitéConditions d'utilisation
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·

7 dépôts

Awesome GitHub RepositoriesStandardized Error Traits

Defines a common Error trait with description, detail, and cause methods that all error types implement.

Distinct from Error Handling: Distinct from Error Handling: specifically defines the standard Error trait interface, not general error handling patterns.

Explore 7 awesome GitHub repositories matching software engineering & architecture · Standardized Error Traits. Refine with filters or upvote what's useful.

Awesome Standardized Error Traits GitHub Repositories

Trouvez les meilleurs dépôts grâce à l'IA.Nous recherchons les dépôts les plus pertinents grâce à l'IA.
  • dtolnay/anyhowAvatar de dtolnay

    dtolnay/anyhow

    6,569Voir sur GitHub↗

    Anyhow is a dynamic error handling library for Rust applications that provides a flexible error container using type erasure. It serves as a tool for simplifying error signatures by wrapping diverse failure types into a single object, allowing for the propagation of any error that implements the standard error trait without requiring a custom enumeration for every function. The project functions as an error context provider by attaching high-level diagnostic information and recording execution stack traces at the point of failure. It enables the recovery of concrete error implementations from

    Provides a trait-object based wrapper for managing diverse error types without custom enums.

    Rust
    Voir sur GitHub↗6,569
  • threedotslabs/wild-workouts-go-ddd-exampleAvatar de ThreeDotsLabs

    ThreeDotsLabs/wild-workouts-go-ddd-example

    6,348Voir sur 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

    Uses agnostic error types and slugs to communicate failures consistently regardless of the delivery mechanism.

    Goclean-architecturecqrsddd
    Voir sur GitHub↗6,348
  • rust-lang/rfcsAvatar de rust-lang

    rust-lang/rfcs

    6,406Voir sur GitHub↗

    The Rust RFCs repository is the formal home for the Rust language evolution process, housing the structured design documents and community review mechanisms that govern changes to the Rust programming language, its compiler, and its standard library. It defines the complete lifecycle for proposing, discussing, and implementing substantial changes through RFC documents, from initial submission and community feedback through final comment periods and sub-team sign-offs. The repository codifies the governance and collaboration processes that shape Rust's development, including mechanisms for com

    Defines the standard Error trait with description, detail, and cause methods for all error types.

    Markdownrfcrfc-processrust
    Voir sur GitHub↗6,406
  • inngest/inngestAvatar de inngest

    inngest/inngest

    5,499Voir sur GitHub↗

    Inngest is a durable execution framework and event-driven automation engine designed to orchestrate background workflows. It enables developers to build resilient, stateful processes by memoizing function steps, ensuring that long-running tasks can automatically resume from the last successful operation after failures, timeouts, or infrastructure restarts. The platform distinguishes itself through its event-driven architecture, which uses a schema-validated bus to trigger functions and coordinate complex, multi-step logic. It employs an onion-model middleware approach for cross-cutting concer

    Intercepts step failures to enable custom recovery logic and exception transformation.

    Go
    Voir sur GitHub↗5,499
  • dry-python/returnsAvatar de dry-python

    dry-python/returns

    4,310Voir sur GitHub↗

    Returns est une bibliothèque de programmation fonctionnelle pour Python qui fournit des conteneurs typés pour gérer l'état, la gestion d'erreurs et l'optionalité. Elle sert de bibliothèque de conteneurs monadiques et de framework de gestion d'erreurs typé, remplaçant les blocs try-catch traditionnels et les vérifications de nullité par des conteneurs Result et Optional pour traiter les exceptions comme des données. Le projet se distingue par son utilisation d'un plugin d'analyse statique Mypy spécialisé pour valider les pipelines fonctionnels et émuler des types d'ordre supérieur. Il fournit des mécanismes pour isoler les effets de bord via des conteneurs IO et offre un framework pour l'injection de dépendances typée qui diffère la fourniture des dépendances jusqu'à l'exécution finale d'un calcul. La bibliothèque couvre un large éventail de primitives fonctionnelles, incluant le currying, l'application partielle et la composition de pipelines de données déclaratifs. Elle prend en charge la gestion de workflow asynchrone en enveloppant les coroutines dans des conteneurs pour enchaîner des opérations non bloquantes et inclut des utilitaires pour la gestion du cycle de vie des ressources et la vérification des lois algébriques pour les conteneurs personnalisés.

    Uses containers to represent success or failure, enabling a linear data flow without try-catch blocks.

    Python
    Voir sur GitHub↗4,310
  • johnsundell/swifttipsAvatar de JohnSundell

    JohnSundell/SwiftTips

    4,014Voir sur GitHub↗

    SwiftTips is a curated collection of guides, libraries, and design patterns focused on Swift language mastery, application architecture, and API design. It provides a technical resource for implementing advanced coding techniques and architectural best practices. The project emphasizes creating type-safe and conversational interfaces through strategic protocol composition and generics. It offers specialized patterns for building modular UI systems and managing complex view hierarchies, alongside comprehensive strategies for unit testing and dependency injection. The resource covers a broad s

    Defines a consistent error reporting interface to standardize how modules communicate failures.

    Voir sur GitHub↗4,014
  • go-errors/errorsAvatar de go-errors

    go-errors/errors

    1,005Voir sur GitHub↗

    errors is a Go error handling library and stack trace utility that wraps standard errors with execution call stacks and contextual information. It captures program execution paths at the exact moment an error is initialized, extracting granular file paths, line numbers, and function symbols from raw program counter addresses. The library maintains parent-child relationships between wrapped errors to allow deep inspection, unwrapping of root causes, and combination of multiple errors into unified structures. It implements standard error interfaces so enhanced error objects can be used intercha

    Enhances standard errors with additional context and stack trace data without losing the original error message.

    Go
    Voir sur GitHub↗1,005
  1. Home
  2. Software Engineering & Architecture
  3. Error Handling
  4. Standardized Error Traits

Explorer les sous-tags

  • Agnostic Error SlugsStandardized error identifiers that communicate failures consistently across different delivery mechanisms. **Distinct from Standardized Error Traits:** Distinct from error traits by focusing on the use of human-readable slugs for delivery-agnostic error identification.
  • Dynamic Error ContainersWrappers that use trait objects to hold any error implementing a standard trait. **Distinct from Standardized Error Traits:** Focuses on the container's ability to hold any error, rather than just the definition of the trait.
  • Step Failure HandlersIntercepts step failures to transform exceptions or trigger custom recovery logic. **Distinct from Standardized Error Traits:** Distinct from Standardized Error Traits: focuses on the interception and recovery logic for workflow steps rather than defining error traits.