Libraries tagged by definitions

Fake "Belastingdienst" domain definition files

Go to Download

A Laravel package to auto-generate Fillable to models from table definitions.

Go to Download

A Laravel package to auto-generate models and migrations from table definitions.

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

The form component is used to validate data against the field definitions of a form.

Go to Download

Used in JW3B Core for language definitions

Go to Download

MvcCore Application - Questionnaires & Statistics - more complex example how to build very portable app with questionnaires definitions in XML, any question types also defined in XML and answers and anonymous statistics stored and loaded from mysql/mssql database.

Go to Download

Extending Imagine filters for easier filter definition

Go to Download

A simple PHP class for validating variable types, fixing, sanitising and setting default values for a model definition encoded as an array.

Go to Download

Dispatches jobs by convention to separate handler class located next to job definition

Go to Download

Translate yaml schema definitions into real actual databases

Go to Download

Command the power of WORDS! Summon definitions! Do thesaurus stuff! This is a wrapper for the Words API

Go to Download

The interface definitions for the Quick framework.

Go to Download

Fix redirect loops when using both environment store definition and locale switcher.

Go to Download

Interface definition for PSR-7 compliant HTTP message transport handler

Go to Download