Human friendly errors for your APIs & projects.
Human-readable error messages for Ajv (Another JSON Schema Validator).
Transforms ajv errors into human readable messages that can be displayed to end users. (Fork https://github.com/segmentio/action-destinations/tree/main/packages/ajv-human-errors)
Human-friendly JSON Schema validation for APIs
Throw, identify, and decode Solana JavaScript errors
Human-friendly process signals
Custom error types and error factory functions
JSON Schema validation for Human
User interface primitives for console applications
JSON Schema validation for Human
Prettified AJV errors
JSON Schema validation for Human
No description provided.
JSON Schema validation for Human
A script to fix simple human errors in writing down seed phrases for Algorand.
Returns from a pool of 15m human-readable IDs
This package brings together every error message across all Wallet Standard JavaScript modules.
A simple cache for a few of the JS Error constructors.
Create HTTP error objects
Svelte Code Checker Terminal Interface
Save a baseline of TypeScript errors and compare new errors against it. Useful for type-safe feature development in TypeScript projects that have a lot of errors. This tool will filter out errors that are already in the baseline and only show new errors.
POSIX-style errors, logging, and more
JSON.parse with context information on error
TypeScript definitions for http-errors
DSL evaluation library. It produces a human-friendly backtrace error
This makes possible to translate the XML errors generated by the schema using I18n
This gem appends a new message to the standard exception message, written from the perspective of a person instead of a complier.
This is not rocket science at all, this gem just adds a helper method to retrieve human friendly errors from ActiveRecord models.
Gem enables to override error messages keys for pretty rendering
Easily configure human readable error messages for your exception classes, or for classses declared in libraries you use.
The WindowsError gem provides an easily accessible reference for standard Windows API Error Codes. It allows you to do comparisons as well as direct lookups of error codes to translate the numerical value returned by the API, into a meaningful and human readable message.
trex is script simplifying the compilation of latex files by creating proper human-readable error output with repeating patterns. Unlike the original latex output which is oververbosified.
Provides a (hopefully) simpler way of localising the human name, attribute names, and error message for ActiveRecord models.
ConciseErrors replaces ActionDispatch::DebugExceptions with a compact error page that highlights the exception and a truncated backtrace, making Rails crashes easier for humans and AI helpers alike.
Sixword encodes binary data in a human-friendly format using English words. It uses the 6-word binary encoding created for S/Key (tm) and standardized by RFC 2289, RFC 1760, and RFC 1751. Binary data is encoded using a dictionary of 2048 short English words (1-4 letters in length). Each block of 64 bits is encoded using 6 words, which includes 2 parity bits for error checking. This is ideal for transmitting binary data such as cryptographic keys where humans must communicate or enter the values. See also: Bubble Babble, PGP Word List, Diceware, Base64, Base32
Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.