Libraries tagged by custom-rules

Custom rules for php-cs-fixer

Go to Download

Custom rules for PHP_CodeSniffer

Go to Download

Some custom PHPStan extensions for a better code base

Go to Download

Rector custom rules

Go to Download

Advanced validation library with multiple API styles including JSON templates, inline rules, builder pattern, and functional composition. Features 50+ built-in validators, dot notation for nested objects, field reference resolution, and internationalization support. Zero dependencies, fully synchronous, and designed for maximum developer experience with extensible custom rule system.

Go to Download

A comprehensive PHP validation library with support for 50+ validation rules, custom rules, profiles, and multi-language error messages

Go to Download

Laravel custom rule to detect role-based emails.

Go to Download

Custom validation rules for Laravel

Go to Download

Package to extract and provide PHPStan source code for developing custom rules

Go to Download

Publish fully compliant Google Merchant Center feeds with automated scheduling. Map Magento attributes to Google product schema using presets or custom rules. Produce supplemental feeds for promotions, sale pricing, and inventory. Validate feed output with warnings before pushing to Merchant Center. Automate uploads via SFTP, Content API, or downloadable URLs. Fully compatible with Magento 2.4.x Open Source and Adobe Commerce. Need feed setup or ongoing support? See our Magento development services, Magento maintenance services, and Magento hosting solutions.

Go to Download

Aura filter 2.x additional custom rule module

Go to Download

Role-based access control (RBAC) with custom rules (like ABAC)

Go to Download

Laravel custom rule for validate pin numbers in INDIA

Go to Download

**Send emails fast and with confidence through our easy to use [REST](https://en.wikipedia.org/wiki/Representational_state_transfer) API interface.** # Overview This is the API interface to the [Mail Baby](https://mail.baby/) Mail services provided by [InterServer](https://www.interserver.net). To use this service you must have an account with us at [my.interserver.net](https://my.interserver.net). # Mail Orders Every sending account in MailBaby is backed by a **Mail Order** — a provisioned sending credential with a numeric `id` and a corresponding SMTP username (`mb`). Most calls accept an optional `id` parameter; when omitted the API automatically selects the first active order on your account. Use `GET /mail` to list all orders, and `GET /mail/{id}` to inspect a single order including its current SMTP password. # Sending Email Three sending methods are available depending on your use-case: | Endpoint | Best for | |----------|----------| | `POST /mail/send` | Simple single-recipient messages | | `POST /mail/advsend` | Multiple recipients, CC/BCC, attachments, named contacts | | `POST /mail/rawsend` | Pre-built RFC 822 messages (e.g. DKIM-signed payloads) | After a successful send each endpoint returns a `GenericResponse` whose `text` field contains the **transaction ID** assigned by the relay. This ID can later be matched against entries in `GET /mail/log` via the `mailid` query parameter. # Filtering & Logs `GET /mail/log` provides paginated access to every message accepted by the relay for your account. Combine any of the query parameters to narrow results — e.g. `from`, `to`, `subject`, `messageId`, `origin`, `mx`, `startDate`/`endDate`, and `delivered`. # Blocking Two independent mechanisms exist for suppressing unwanted email: - **Block lists** (`GET /mail/blocks`, `POST /mail/blocks/delete`) — addresses flagged by the system spam filters (LOCAL_BL_RCPT / MBTRAP rules in rspamd, and suspicious subjects). - **Deny rules** (`GET /mail/rules`, `POST /mail/rules`, `DELETE /mail/rules/{ruleId}`) — custom rules you configure to reject specific senders, domains, destination addresses, or subject-line prefixes before a message is even attempted. # Authentication In order to use most of the API calls you must pass credentials from the [my.interserver.net](https://my.interserver.net/) site. We support several different authentication methods but the preferred method is to use the **API Key** which you can get from the [Account Security](https://my.interserver.net/account_security) page. Pass your key in the `X-API-KEY` HTTP request header for every protected call.

Go to Download

PHPStan custom rules for Edhrendal projects

Go to Download