Libraries tagged by object tools

pamiris/javascript-constants

1 Favers
163 Downloads

A simple tool for converting PHP constant classes into javascript constant objects

Go to Download


mapkyca/console-entitydump

0 Favers
14 Downloads

A tool for outputting the raw contents of an object as identified by UUID, ID or short url

Go to Download


lkcodes/mycode

1 Favers
42 Downloads

A collection of commonly used tools, such as exporting tables, manipulating databases,File caching, string processing/encoding and decoding, array and object conversion, and so on. It can be used in any framework

Go to Download


fwrepae/fwrepae

0 Favers
0 Downloads

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


elcontraption/wp-post-inspector

0 Favers
353 Downloads

Tools for interacting and inspecting WordPress post objects.

Go to Download


christoph-kluge/dns

1 Favers
23 Downloads

This library aims to give you an object oriented wrapper around the php's dns network tools.

Go to Download


agrandesr/response

0 Favers
2 Downloads

This is a simple Tool for create data responses for APIs. The idea is that you can use the object response throught your code and print a complete response at final.

Go to Download


atk4/core

20 Favers
1846798 Downloads

Agile Core - collection of PHP Traits for designing object-oriented frameworks

Go to Download


pimcore/frontend-permission-toolkit-bundle

21 Favers
94694 Downloads

Provides a way to configure permissions for frontend applications in data objects.

Go to Download


elements/export-toolkit-bundle

12 Favers
4057 Downloads

The Export Toolkit provides functionality to configure exports of Pimcore objects

Go to Download


jameswatts/cake-toolkit

49 Favers
3294 Downloads

Define your View as a class, providing a powerful object-oriented factory interface to dynamically build your CakePHP application UI with configurable objects

Go to Download


mncee/salesforce-sync

4 Favers
1238 Downloads

Package for syncing Salesforce objects with local data

Go to Download


moehrenzahn/wp-toolkit

6 Favers
71 Downloads

An object-oriented framework around common WordPress functionality to jumpstart theme and plugin development.

Go to Download


jameswatts/cake-factory

9 Favers
1396 Downloads

Cake is a factory for the Cake Toolkit (CTK) which provides configurable objects for the core helpers in CakePHP

Go to Download


ttree/neos-toolbox

0 Favers
202 Downloads

A toolbox of Node Types and TypoScript2 objects for TYPO3 Neos.

Go to Download


<< Previous Next >>