Libraries tagged by shcc

marcosdsanchez/chainable

2 Favers
17 Downloads

An easy way to chain responsibilities until a successful response is given or the chain finishes.

Go to Download


lulubin/yii2-widget-alert

0 Favers
0 Downloads

An Yii2 widget for alert after create or update successfully

Go to Download


lsbr/messageadditionalsuccesspage

0 Favers
0 Downloads

Magento 2 Module for add message in success page

Go to Download


leonard/route-generator

0 Favers
1 Downloads

Generates the route with highest success chance from the given tickets

Go to Download


leibbrand-development/php-docker-client

0 Favers
23 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.41) is used. For example, calling `/info` is the same as calling `/v1.41/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 [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (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


krylov123/handy-api-response

0 Favers
12 Downloads

Simple and handy Class for API Responses with success flag, errors bag and data property

Go to Download


kayobruno/http-status-code

0 Favers
0 Downloads

The "HTTP Status Code Abstraction" project is a PHP 8-based initiative aimed at simplifying the management and usage of HTTP status codes by introducing ENUM support. HTTP status codes are integral to web development, providing vital information about the success or failure of HTTP requests and responses. However, managing and referencing these status codes in a clear and organized manner can often be challenging. This project seeks to address this challenge by leveraging PHP 8's ENUM feature.

Go to Download


jezuu/notifications

0 Favers
27 Downloads

Notifications is a Laravel package that offers a comprehensive solution for displaying notifications in your application. It provides predefined components and styles for showcasing success messages, errors, warnings, and informative messages in an appealing manner. With this package, you can easily customize the notification type, the accompanying icon, and the displayed message. It seamlessly integrates with popular libraries like Font Awesome and Bootstrap Notify to deliver a sleek and user-friendly notification experience. Save time and enhance the presentation of your notification messages with Notifications package for Laravel.

Go to Download


janhelke/calendar-foundation

0 Favers
324 Downloads

The foundation for the calendar. At the core it is the successor of ext:cal.

Go to Download


jakesutherland/nomad-forms

0 Favers
4 Downloads

A WordPress PHP Composer Package that provides you with an easy way to display and process forms, render and validate fields, and display error/success messages.

Go to Download


jackyliu/ftp

0 Favers
172 Downloads

Wannabe successor of anchu/ftp package for Laravel

Go to Download


ider/flashmessages

0 Favers
9 Downloads

FlashMessages is a class to handle success, debug, warning and error messages. It's made for the framework Anax-MVC.

Go to Download


hilalahmad/php-toastr

0 Favers
8 Downloads

The PHP Toastr package is a user-friendly and lightweight PHP library designed to create simple and stylish notification messages in web applications. It offers a convenient way to display various types of notifications, such as success messages, error alerts, information pop-ups, and more, in a visually appealing manner to enhance the user experience.

Go to Download


gueststream/bookingconfirmation

0 Favers
18 Downloads

Booking confirmation class used in response to successful bookings.

Go to Download


giofreitas/wordpress

1 Favers
19 Downloads

Just a package that set everything you need to get WordPress running successfully with composer.

Go to Download


<< Previous Next >>