Enhanced Error class for creating meaningful and customizable error classes. Adds option to remove stacktrace and format the toString method.
Turns errors from database libraries into more useful error objects
An useful error handler for axios network requests in a React application
ensures all required parameters are not null, or throws a useful error like 'phone is required'
Useful error stacks for development that include code highlighting.
Checks that two objects are equal and gives useful error message
Klaxon is a framework for producing *useful* error messages.
HTTP-friendly error objects
throw a useful error when generator functions arent available
Selective error catching and rewrite rules
Useful TypeScript utilities.
No description provided.
Topological sorting with grouping support
General purpose node utilities
Email address and domain validation
Object schema validation
OpenTelemetry OTLP Exporter base (for internal use only)
Math and string formula parser.
richer JavaScript errors
Return the filename and line number of the calling function
Email address and domain validation
OpenTelemetry OTLP-gRPC Exporter base (for internal use only)
TLDS list for domain validation
JSON parse with prototype poisoning protection
Backported from Rails 5.0 to use with 4.x versions
If you use a finder that reaches capybara's timeout, and error is raised.
ActiveRecord::DebugErrors is an extension of activerecord to display useful debug logs on errors.
Uses the asset pipeline to generate your static error pages.
Render ERB template and provide more useful message pointing out the line with the error in the view
Business Error Management by using OOP
Internal errors library used by the Fanforce codebase.
Internal errors library used by the Fanforce codebase.
Compile Flex in Textmate using FCSH. Advanced error reporting.
Secure applications disable browser history and internal cache. Unfortunately, this causes problems with most browsers when following the standard Rails pattern for displaying errors. For full protection from ERR_CACHE_MISS (in Chrome with no-cache, no-store), and equivalent in other browsers, the pattern should be altered to follow a full POST-REDIRECT-GET patten. This way the browser will always have a consistent back-button history to traverse without triggering browser errors.
Generate Rails error pages on deployment using application controller renderer
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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.