Libraries tagged by object parameter

A function/method/invokable-object parameter resolution utility class

Go to Download

Convert method parameters and object properties

Go to Download

This library is a Singleton (anti)pattern implementation using a Traits with a support for an Object Inheritance and passing parameters to the constructor.

Go to Download

Object method mapping by parameter type

Go to Download

Just a side project after getting tired of hearing people grip out parameter orders and other such nots with build in variables.

Go to Download

A simple data transfer object

Go to Download

Handle HTTP request that calls a specified static class function given serialzed objects as parameters in the request

Go to Download

Symfony bundle to be able to use object request parameter

Go to Download

Creation of objects by parameters

Go to Download

Parse request parameters to object.

Go to Download

Dynamic factory to create objects reading the parameters of the construct method

Go to Download

Binance API is a PHP library based on simplified CQRS and Value Objects. Contains validation of parameters sent to API binance according to the documentation.

Go to Download

Aggregates input parameters from http request into one object and apply validation rules to them

Go to Download

Bundle that provides aviability of generating URL address to objects instead of giving route name and route parameters

Go to Download

The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>

Go to Download