Libraries tagged by HTML Generator

E-mail signature code generator for Statamic

Go to Download

Laravelium Sitemap package for Laravel.

Go to Download

Generate a self-contained static website from explicitly registered Laravel routes and page sources

Go to Download

Laravelium Sitemap package for Laravel.

Go to Download

Make to add new feature in JscDev/laravel-table.

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

Laravelium Sitemap package for Laravel.

Go to Download

Sitemap package for Laravel. forked from laravelium sitemap package

Go to Download

Generate tables with Laravel.

Go to Download

# Overview The ELMO API is a RESTful based API that facilitates user information management within the ELMO ecosystem. Our API is designed to empower businesses, including our valued customers and partners, in creating scalable integration solutions aligned with their evolving business needs. By using this API, you gain access to invaluable HR data, enabling you to supercharge your applications and integrations, driving efficient workflows and enhancing core business processes. The below section provides an overview of the current capabilities of the API: * Get users list * Get an individual user's details * Get a user template to create a new user * Create new user * Get positions list * Get locations list * Get department list * Get metadata of configurable fields * Get all users employment details * Get an individual user's employment details * Get legal entity details * Get payroll calendar details * Get leave request details * Get leave type details Note that this is the latest version of the API Documentation that utilises OAuth2 authentication. The previous version of the documentation can be found at [API Documentation version 1](/v1/index.html) Please be advised that endpoints labelled as beta are intended for customer testing and feedback and may change based on feedback, potentially impacting backward compatibility. Consider this before integrating it with production systems to avoid disruptions to your integrations. --- # Authentication ELMO API utlises OAuth2.0 authentication. Company Admins are able to create and manage API Credentials. --- # API Rate Limits There are limits applied to the number of API requests your application can make. This limit is lower in sandbox and higher in production environments. The ELMO User API also supports custom usage plans to scale with your organisation's needs. Sandbox Environment * **Rate limit**: 1 request per second * **Burst limit**: 10 * **Quota**: 500 requests in 1 day Production Environment * **Rate limit**: 1 requests per second * **Burst limit**: 10 * **Quota**: 5000 requests in 1 day --- # Generating Client SDKs You can use the OpenAPI Specification file to generate a client SDK. You can download the file from [here](index.yaml). Then use the tool of your choice to generate a client SDK. You can get started [here](https://swagger.io/tools/swagger-codegen/).

Go to Download

This form is use to generate HTML form using PHP

Go to Download

Laravelium Sitemap package for Laravel. Taken over by Dragon Zap

Go to Download

Simple DOM generator inspired by Emmet

Go to Download

PDF generation from a url or a html page

Go to Download

Генерация штрихкодов для PHP 8.1+ без внешних зависимостей и расширений: 76 типов символогий — линейные, товарные GS1, почтовые, российские (Честный ЗНАК, ЕГАИС, ШПИ Почты России) и двумерные (DataMatrix, PDF417, Aztec, Han Xin); шесть форматов вывода: SVG, PNG без ext-gd, EPS, HTML, текст и JSON. Вывод выверен байт-в-байт против эталонных реализаций и прочитан независимыми декодерами. Строгая типизация, 100% покрытие и мутационное тестирование.

Go to Download