Libraries tagged by Notch

My own starter Laravel project, nothing fancy, just my things.

Go to Download

WordPress functions that return nothing.

Go to Download

Yet another MongoDB ODM for PHP. Nothing unnecessary, with easy joins.

Go to Download

An empty package that does nothing for init composer

Go to Download

nothing

Go to Download

Nothing to talk

Go to Download

nothing

Go to Download

Magic means nothing yet :-)

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

Only For test. Nothing else.

Go to Download

Bot guard for Flarum 2, on your own server: turn away AI crawlers you don't want, verify real search engines by DNS, give suspicious clients a quick proof-of-work check, rate-limit bursts and keep a log for staff. No Cloudflare, no third-party captcha, nothing added for members.

Go to Download

maybe nothing here;

Go to Download

Intercepts every chat request that leaves the site through the AI module's provider proxy and sends the ones made on behalf of anonymous visitors to a cheaper provider and model, while a request made for an account keeps whatever the calling code chose. Nothing in the model calls an AI provider: it listens to the "AI request: before provider call" event that the ai_eca_interceptor submodule of AI Integration - ECA exposes, so it governs calls made by AI Assistants, automators, agents and custom code alike without owning any of them. The reroute is recorded as intent and executed by a subscriber that runs last, and it fails open - if the target provider throws, the originally chosen one answers instead. Requires the AI module at 1.4 or newer, and the provider and model ids in the reroute action have to be changed to a target configured on your site.

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

Übergangspaket ohne Code: Ekkon (Task-System, Benachrichtigungen, Webhook-Eingang) ist fester Bestandteil der Intranet-Plattform. Das Paket erfüllt nur noch bestehende require-Einträge.

Go to Download