Libraries tagged by form errors
memio/linter
313389 Downloads
Memio's linter, a set of constraint that check models for syntax errors
lucidtaz/yii2-whoops
25407 Downloads
Yii2 bindings for Whoops error handler
deinte/laravel-blade-validator
3434 Downloads
Validate Blade templates for syntax errors, security issues, and best practices
brandonsavage/booboo
740 Downloads
Provides an error handler for PHP that can execute a stack of handlers for various purposes.
sugarcraft/sugar-toast
1336 Downloads
PHP port of DaltonSW/bubbleup — floating alert notification component for terminal UIs. Supports error/warning/info/success alerts at 6 screen positions, dynamic width, NerdFont/Unicode/ASCII symbols, auto-dismiss timers.
sandermuller/json
2267 Downloads
Typed JSON encoding and decoding for PHP with strict error handling and shape assertions.
moxio/captainhook-psalm
62939 Downloads
Captain Hook Plugin to check for newly introduced Psalm errors
mglaman/phpstan-junit
744457 Downloads
ErrorFormatter for PHPStan to output errors in JUnit format
thesis/grpc-protocol
375 Downloads
Shared gRPC protocol runtime for PHP: framing, metadata, status/error model, and encoding/compression primitives used by client and server.
northwestern-sysdev/chassis
5667 Downloads
Shared Laravel infrastructure for audited models, idempotent seeders, API error handling, configuration validation, and more.
netlogix/nxerrorhandler
41093 Downloads
Error handler with static pages for TYPO3
iamfarhad/laravel-prometheus
2250 Downloads
Production-ready Laravel Prometheus metrics package with built-in collectors for HTTP, database, cache, queue, events, errors, filesystem, and mail monitoring
sunnysideup/dataintegritytests
2070 Downloads
check your database for obsolete fields and related data-structure errors
zetacomponents/debug
476519 Downloads
This component provides a set of classes that help you to debug an application. It provides timers and report generators for different formats that give a summary of warnings and errors that occurred within your application.
vitexsoftware/rbczpremiumapi
445 Downloads
##### API Overview - Accounts list and balance - Transaction overview (also for saving accounts) - Payments import - Statement list and download - FX rates ##### Authentication Before making a call to Premium API, you need to register your app at our _Developer portal_. This is where you get the **ClientID** that your application must send in the request as `X-IBM-Client-Id`. This is the key that grants your app access to the API. However, this may not be enough. Your application needs to use mTLS to call most operations here. Thus, you not only need _https_ but also a client certificate issued by us. The exception is two operations for FX rates that are accessible also without a client certificate. Each bank client/user can issue several certificates. Each certificate can permit different sets of operations (http methods) on different bank accounts. All this must be configured in Internet Banking first by each bank client/user (bank clients need to look under _Settings_ and do not forget to download the certificate at the last step). The certificate is downloaded in **PKCS#12** format as **\*.p12** file and protected by a password chosen by the bank client/user. Yes, your app needs the password as well to get use of the **\*p12** file for establishing mTLS connection to the bank. Client certificates issued in Internet Banking for bank clients/users have limited validity (e.g. **5 years**). However, **each year** certificates are automatically blocked and bank client/user must unblock them in Internet Banking. It is possible to do it in advance and prolong the time before the certificate is blocked. Your app should be prepared for these scenarios and it should communicate such cases to your user in advance to provide seamless service and high user-experience of your app. ##### Rate Limiting The number of requests in each API operation is limited to 10 per client per sliding second and 5000 per client per sliding day. The exception is the 'Download Statement' operation with the limits lowered to 5 per client per sliding second and 1500 per client per sliding day. This is because it transports potentially sizeable binary files. The consumer must be able to handle HTTP status 429 in case of exceeding these limits. Response headers `X-RateLimit-Limit-Second` and `X-RateLimit-Limit-Day` show the actual limits configured for the specific operation. Response headers `X-RateLimit-Remaining-Second` and `X-RateLimit-Remaining-Day` are returned to help prevent the limits from being exceeded. ##### Notes Be aware, that in certain error situations, API can return specific error structures along with 5xx status code, which is not explicitely defined below. ##### Quick Start Client Feel free to download a simple Java client that gives you quick access to our API.