Check whether a DOM element is contained by another one
Return true if a file path contains the given path.
No description provided.
This package contains misc utilities for Lexical.
Check if a buffer contains valid UTF-8
This package contains selection offset helpers for Lexical.
This package contains the functionality for Lexical hashtags.
A term-contains function-factory actor
Test if an array-like value contains a search value.
This package contains the functionality for Lexical links.
Test if an array contains a provided search value.
This package contains compatibility with Dragon NaturallySpeaking accessibility tools.
This package contains the JSON schema for the Redocly configuration file.
Validates if an array contains an input value.
Contains constants for torus and web3auth
This package contains utilities and helpers for handling Lexical text.
This package contains selection overflow helpers and nodes for Lexical.
This package contains utilities and helpers for handling Lexical selection.
This package contains selection history helpers for Lexical.
This package contains tools necessary to debug and develop Lexical.
`Node#contains()` cross browser polyfill
TypeScript definitions for contains-path
contains typescript types for salesforce objects
Clack contains low-level primitives for implementing your own command-line applications.
A Container trait
A complete library to interact with Tag Manager (protocol v2)
Python bindings to the docker-api-rs crate
Docker/Container component for rust-camel — run, manage and listen to container events via the Camel routing engine
Elegant and extensible assertions in rust.
Abstract over "containers" that hold a T, such as a T itself, Box<T>, or Arc<Mutex<T>>
A modern, feature-rich testing framework for Rust with Docker integration
An intuitive Docker management CLI built in Rust with full Docker command parity
A complete library to interact with Tag Manager (protocol v2)
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.42) is used. For example, calling `/info` is the same as calling `/v1.42/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..." } ```
Fluent test assertions
A complete library to interact with Tag Manager (protocol v1)
Extends puppet-lint to ensure that your variables are all lower case
Check if points are inside or outside the region polygons in an imported KML file.
A simple, configurable object container implemented in Ruby
A self-contained `tailwindcss` executable, wrapped up in a ruby gem. That's it. Nothing else.
Container-agnostic automatic constructor injection
Dependabot-Devcontainers provides support for managing dev container versioning via Dependabot.
Official AWS Ruby gem for Amazon EMR Containers. This gem is part of the AWS SDK for Ruby.
The Ruby Container for Henry
JRuby-Rack is a combined Java and Ruby library that adapts the Java Servlet API to Rack. For JRuby only.
Library that contains the classes required to create LogStash events
Deploy Docker container
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.