Libraries tagged by hash code

Model Has Organization

Go to Download

This module provide Node/Media has term with URI conditions

Go to Download

This group of methods for work with tree structure. Provide methods build tree from flat array, find node in the tree by id, walk tree and execulte callback function for each node. Node of the tree has fields like as id, parent_id, children. Concrete names of the tree node fields can be configured with TreeAlgorithms properties idFieldName, parentIdFieldName, childsFieldName. Also exists javascript release, search lamzin-andrey/landlib on github.

Go to Download

Laravel eloquent has a lot in the model class, this package helps with separating the concerns away from just the model

Go to Download

This behavior class allows you to specify an attribute which, upon setting or being set, prevents the model from being changed. Think of it as a latch that locks the model once a particular value has been set and saved.

Go to Download

Scores every newly submitted comment for toxicity and spam with one AI call that returns a strict JSON verdict, then routes that verdict through ordinary ECA conditions into one of three exits: publish, hold for review, or block. The thresholds are two "Token: set value" actions in the model, not numbers in the prompt, so the policy can be changed without touching the prompt. Every run writes both scores, both thresholds and the exit taken to the eca_comment_verdict log channel, and a failed or undecodable AI response holds the comment instead of publishing it. Requires the ai_integration_eca and eca_tamper contributed modules, and a chat model that supports structured output has to be selected in the "Ask AI to score the comment" action.

Go to Download

web site package has crud operation , middleware , template mastering , custom facade , dependency ingection and model , migration files!

Go to Download

PHP HTML Builder - A Lightweight Alternative to LaravelCollective/HTML and Spatie/Laravel-HTML With the release of Laravel 11, support for laravelcollective/html has been discontinued, leaving many developers searching for a modern, simple solution to generate HTML and form elements. PHP HTML Builder is here to fill that gap — offering a streamlined, intuitive alternative compatible with Laravel 9, 10, and 11. This package provides an easy-to-use, fluent API that replicates the functionality of laravelcollective/html and spatie/laravel-html, enabling developers to effortlessly create HTML components, forms, inputs, checkboxes, radio buttons, dropdowns, links, images, and more. Built with simplicity and flexibility in mind, PHP HTML Builder is a lightweight, PHP-first solution for building and managing dynamic user interfaces in Laravel applications.

Go to Download

The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.

Go to Download

An external MCP assistant drafts a conference talk with a user and submits it to Drupal, which owns every rule. The model publishes two tools: one submits, the other answers what a submission has to look like - the window, the accepted levels, the tracks the site currently offers and the duration limit for a level - so the assistant asks instead of exploring the site. Both run the same policy actions, so the rules an assistant is told are the rules it is held to. The submitting tool turns its five arguments into tokens, checks the submission window, the audience level, the track and a per-level duration limit before anything is written, and returns a structured result either way. The speaker is taken from the authenticated account and is not a tool argument. A valid proposal is created unpublished in the talk_review workflow, awaiting human review, and the result carries a link to it. The beginner duration rule is a single action in the diagram, which both tools read, so changing it live changes what the tools do and what they advise with no change on the assistant side.

Go to Download

Demonstrates how to express an if/elseif/else decision in an ECA model, the pattern people usually reach for when they want a PHP switch statement. ECA has neither a switch construct nor a working exclusive gateway, so the model uses the sentinel-default idiom instead: it assigns the default value up front, lets a matching branch overwrite it, and then, one hop downstream, tests whether the value is still the default in order to detect that nothing matched. Along the way it demonstrates the four-links-to-one-target OR idiom, in which several conditioned links leaving the same predecessor point at the same successor, so that any one of them is enough to run it.

Go to Download

# Summary The **NextGenPSD2** *Framework Version 1.3.6* (with errata) offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGenPSD2 Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe and, aligned with the goals of the Euro Retail Payments Board, enables European banking customers to benefit from innovative products and services ('Banking as a Service') by granting TPPs safe and secure (authenticated and authorised) access to their bank accounts and financial data. The possible Approaches are: * Redirect SCA Approach * OAuth SCA Approach * Decoupled SCA Approach * Embedded SCA Approach without SCA method * Embedded SCA Approach with only one SCA method available * Embedded SCA Approach with Selection of a SCA method Not every message defined in this API definition is necessary for all approaches. Furthermore this API definition does not differ between methods which are mandatory, conditional, or optional. Therefore for a particular implementation of a Berlin Group PSD2 compliant API it is only necessary to support a certain subset of the methods defined in this API definition. **Please have a look at the implementation guidelines if you are not sure which message has to be used for the approach you are going to use.** ## Some General Remarks Related to this version of the OpenAPI Specification: * **This API definition is based on the Implementation Guidelines of the Berlin Group PSD2 API.** It is not a replacement in any sense. The main specification is (at the moment) always the Implementation Guidelines of the Berlin Group PSD2 API. * **This API definition contains the REST-API for requests from the PISP to the ASPSP.** * **This API definition contains the messages for all different approaches defined in the Implementation Guidelines.** * According to the OpenAPI-Specification [https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md] "If in is "header" and the name field is "Accept", "Content-Type" or "Authorization", the parameter definition SHALL be ignored." The element "Accept" will not be defined in this file at any place. The elements "Content-Type" and "Authorization" are implicitly defined by the OpenApi tags "content" and "security". * There are several predefined types which might occur in payment initiation messages, but are not used in the standard JSON messages in the Implementation Guidelines. Therefore they are not used in the corresponding messages in this file either. We added them for the convenience of the user. If there is a payment product, which needs these fields, one can easily use the predefined types. But the ASPSP need not to accept them in general. * **We omit the definition of all standard HTTP header elements (mandatory/optional/conditional) except they are mentioned in the Implementation Guidelines.** Therefore the implementer might add these in his own realisation of a PSD2 comlient API in addition to the elements defined in this file. ## General Remarks on Data Types The Berlin Group definition of UTF-8 strings in context of the PSD2 API has to support at least the following characters a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / - ? : ( ) . , ' + Space

Go to Download

A package to enable assigning cash to Eloquent Models

Go to Download

Typed JSON-RPC client for Bitcoin Cash Node (BCHN) in pure PHP over any PSR-18 client — wallet, UTXO, PSBT, raw-transaction and double-spend-proof calls in the BCHN dialect, CashTokens token data, exact satoshi amounts, never floats.

Go to Download

Panth MagePos - a full point of sale (POS) for Magento 2. Standalone touch-friendly terminal with cashier authentication and PIN lock, register sessions with cash management and X/Z reports, barcode scanning, quick keys, multi-cart hold/retrieve, discounts with per-role caps, custom sale lines, split payments (cash, offline and online methods), 80mm receipts, refunds, offline mode with order sync, and a drag-and-drop layout editor.

Go to Download