Libraries tagged by shoperti

netsilik/struct

1 Favers
283 Downloads

Getters and setters made easy by rule bound magic methods. Support for Read-only public properties.

Go to Download


neosrulez/neos-uniqueproperties

0 Favers
2 Downloads

Unique properties for Neos CMS.

Go to Download


natsumeaurlia/auto-property-reflection

0 Favers
22 Downloads

Automatically reflect properties.

Go to Download


mohamedahmed00/coollection

0 Favers
2 Downloads

Laravel Illuminate collection with objectified properties

Go to Download


mof/timestampable-bundle

0 Favers
5 Downloads

Symfony bundle for automatically handle creation and update date of Doctrine entity properties

Go to Download


modera/config-bundle

1 Favers
4594 Downloads

Bundles provides tools that allow to you to dynamically store and fetch your configuration properties in a flexible way.

Go to Download


mmamedov/array-property

0 Favers
17 Downloads

Access arrays in an intuitive and object-oriented way. Keys and values are treated as properties.

Go to Download


mks/service_list

0 Favers
29 Downloads

Service list with ability to explore service methods and properties.

Go to Download


misbah/prop-monitor

1 Favers
10 Downloads

This library will help you to check nested php objects whether they have some certain properties or not.

Go to Download


milantex/tpc

0 Favers
13 Downloads

This project provides a mechanism to specify types for class properties. Also, property types have additional parameters, such as the regular expression pattern for strings, minimum and maximum value for integers etc. The special setter method handles type checking and will set the given value only if it is valid for the given type and its additional parameters. Check the documentation for an example.

Go to Download


melting-server/schema-dot-org-tree

1 Favers
10 Downloads

Reads a version of schema.org and builds out a structured tree. Access any entry's direct or inherited properties or traverse the tree using $entity->parent() or $entity->children. Supports multiple schema versions.

Go to Download


mediawiki/smw-user-protect

1 Favers
22 Downloads

Extension for protecting pages from users depending on certain semantic properties

Go to Download


mediawiki/smw-list-props

0 Favers
8 Downloads

Extension for printing out all the different properties associated to a wiki page

Go to Download


mediarox/module-eav-property-mapper

0 Favers
1 Downloads

Allows to use db properties for adding attributes

Go to Download


maxvaer/docker-openapi-php-client

0 Favers
4 Downloads

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download


<< Previous Next >>