Results for form-valid-basic

Aging — last published over a year ago — check before adopting.

FormValidator es una librería para validar formularios de manera sencilla.

@tailwindcss/formsv0.5.11

A plugin that provides a basic reset for form styles that makes form elements easy to override with utilities.

form-datav4.0.5

Aging — last published 6 months ago — check before adopting.

A library to create readable "multipart/form-data" streams. Can be used to submit forms and file uploads to other web applications.

card-validatorv10.0.4

A library for validating credit card fields

@emotion/is-prop-validv1.4.0

Aging — last published 9 months ago — check before adopting.

A function to check whether a prop is valid for HTML and SVG elements

encodeurlv2.0.0

Encode a URL to a percent-encoded form, excluding already-encoded sequences

@material/form-fieldv14.0.0

Abandoned. Last published 4 years ago.

Material Components for the web wrapper for laying out form fields and labels next to one another

@chakra-ui/form-controlv2.2.0

React component to provide validation states to form fields

@apollo/utils.fetcherv3.1.0

Minimal web-style fetch TypeScript typings

multerv2.1.1

Middleware for handling `multipart/form-data`.

react-hook-formv7.77.0

Performant, flexible and extensible forms library for React Hooks

@swup/forms-pluginv3.6.0

Abandoned. Last published over a year ago.

A swup plugin for submitting forms

validate-npm-package-namev8.0.0

Give me a string and I'll tell you if it's a valid npm package name

form-data-encoderv4.1.0

Aging — last published 12 months ago — check before adopting.

Encode FormData content into the multipart/form-data format

autocannonv8.0.0

Abandoned. Last published over a year ago.

Fast HTTP benchmarking tool written in Node.js

tsicklev0.46.3

Abandoned. Last published 3 years ago.

Transpile TypeScript code to JavaScript with Closure annotations.

aws-jwt-verifyv5.1.1

Aging — last published 8 months ago — check before adopting.

Verify JSON Web Tokens (JWT) from Amazon Cognito and other IDPs

@mapbox/geojson-extentv1.0.1

Abandoned. Last published 4 years ago.

compute the bounding box of geojson features

semverv7.8.1

The semantic version parser used by npm.

mantine-form-zod-resolverv1.3.0

Aging — last published 11 months ago — check before adopting.

Zod resolver for @mantine/form validation

is-valid-globv1.0.0

Abandoned. Last published 8 years ago.

Return true if a value is a valid glob pattern or patterns.

copy-descriptorv0.1.1

Abandoned. Last published 9 years ago.

Copy a descriptor from object A to object B

JSON for Humans

Abandoned. Last published 3 years ago.

valid-data-urlv5.0.0

Detect if a string is a data URL

RubyGems matches

4 matches · Ruby

formalizev0.0.4

Abandoned. Last published 13 years ago.

This is a very basic (and untested!) RubyGem to simplify web form creation, validation and processing. It is designed for use with the Sinatra framework.

mostv0.7.7

Abandoned. Last published 16 years ago.

Most is a simple academic modular open software tester. Most, the Core is the main part of the system. Most provides the environment and interface bridges for modules that will implement the basic functionality of the testing system. In general Most, the Core consists form two main interfaces: the connector and the tester. The connector interface offers the basic bridge to make an implementation of a module which will act as a controlling interface of the system. It can be a command line interface or it can be a module which will set up a server providing a network access for end users. The tester interface allows building an implementation of the software validator. By default the Most ships with the tester compliant with the ICPC Validator Standard. The Most system proposes to implement a testing system following this standard, but it is not obligatory. The 3-rd party implementation can vary significantly considering the user preferences. It is possible to build other interface bridges using the abstract interface classes provided by the Most system to extend the functionality of the modules. For example the implementation of the connector interface in the form of the network server can build a tunnel interface bridge, so that developers can make implementations, for example, of a SSH tunnel in order to provide a secure connection with the testing system. The default system bundle is shipped with a number of basic interface implementations (modules). Please, consider taking a look on realize notes for the list of supplied modules.

get_around_ownerv1.0.8

Aging — last published over a year ago — check before adopting.

# Quick Start The Owner API uses the JSON format, and must be accessed over a [secure connection](https://en.wikipedia.org/wiki/HTTPS). Let’s assume that the access token provided by your account manager is “TOKEN”. Here’s how to get the list of ids of all your invoices from the first week of August with a shell script: ```bash query="end_date=2018-08-08T00%3A00%3A00%2B00%3A00&start_date=2018-08-01T00%3A00%3A00%2B00%3A00" curl -i "https://api-eu.getaround.com/owner/v1/invoices?${query}" \ -H "Authorization: Bearer TOKEN" \ -H "Accept:application/json" \ -H "Content-Type:application/json" ``` And here’s how to get the invoice with the id 12345: ```bash curl -i "https://api-eu.getaround.com/owner/v1/invoices/12345" \ -H "Authorization: Bearer TOKEN" \ -H "Accept: application/json" \ -H "Content-Type: application/json"" ``` See the [endpoints section](#tag/Invoices) of this guide for details about the response format. Dates in request params should follow the ISO 8601 standard. # Authentication All requests must be authenticated with a [bearer token header](https://tools.ietf.org/html/rfc6750#section-2.1). You token will be sent to you by your account manager. Unauthenticated requests will return a 401 status. # Pagination The page number and the number of items per page can be set with the “page” and “per_page” params. For example, this request will return the second page of invoices, and 50 invoices per page: `https://api-eu.getaround.com/owner/v1/invoices?page=2&per_page=50` Both of these params are optional. The default page size is 30 items. The Getaround Owner API follows the [RFC 8288 convention](https://datatracker.ietf.org/doc/html/rfc8288) of using the `Link` header to provide the `next` page URL. Please don't build the pagination URLs yourself. The `next` page will be missing when you are requesting the last available page. Here's an example response header from requesting the second page of invoices `https://api-eu.getaround.com/owner/v1/invoices?page=2&per_page=50` ``` Link: <https://api-eu.getaround.com/owner/v1/invoices?page=3&per_page=50>; rel="next" ``` # Throttling policy and Date range limitation We have throttling policy that prevents you to perform more than 100 requests per min from the same IP. Also, there is a limitation on the size of the range of dates given in params in some requests. All requests that need start_date and end_date, do not accept a range bigger than 30 days. # Webhooks Getaround can send webhook events that notify your application when certain events happen on your account. This is especially useful to follow the lifecycle of rentals, tracking for example bookings or cancellations. ### Setup To set up an endpoint, you need to define a route on your server for receiving events, and then <a href="mailto:owner-api@getaround.com">ask Getaround</a> to add this URL to your account. To acknowledge receipt of a event, your endpoint must: - Return a `2xx` HTTP status code. - Be a secure `https` endpoint with a valid SSL certificate. ### Testing Once Getaround has set up the endpoint, and it is properly configured as described above, a test `ping` event can be sent by clicking the button below: <form action="/docs/api/owner/fire_ping_webhook" method="post"><input type="submit" value="Send Ping Event"></form> You should receive the following JSON payload: ```json { "data": { "ping": "pong" }, "type": "ping", "occurred_at": "2019-04-18T08:30:05Z" } ``` ### Retries Webhook deliveries will be attempted for up to three days with an exponential back off. After that point the delivery will be abandoned. ### Verifying Signatures Getaround will also provide you with a secret token, which is used to create a hash signature with each payload. This hash signature is passed along with each request in the headers as `X-Drivy-Signature`. Suppose you have a basic server listening to webhooks that looks like this: ```ruby require 'sinatra' require 'json' post '/payload' do push = JSON.parse(params[:payload]) "I got some JSON: #{push.inspect}" end ``` The goal is to compute a hash using your secret token, and ensure that the hash from Getaround matches. Getaround uses an HMAC hexdigest to compute the hash, so you could change your server to look a little like this: ```ruby post '/payload' do request.body.rewind payload_body = request.body.read verify_signature(payload_body) push = JSON.parse(params[:payload]) "I got some JSON: #{push.inspect}" end def verify_signature(payload_body) signature = 'sha1=' + OpenSSL::HMAC.hexdigest(OpenSSL::Digest.new('sha1'), ENV['SECRET_TOKEN'], payload_body) return halt 500, "Signatures didn't match!" unless Rack::Utils.secure_compare(signature, request.env['HTTP_X_DRIVY_SIGNATURE']) end ``` Obviously, your language and server implementations may differ from this code. There are a couple of important things to point out, however: No matter which implementation you use, the hash signature starts with `sha1=`, using the key of your secret token and your payload body. Using a plain `==` operator is not advised. A method like secure_compare performs a "constant time" string comparison, which renders it safe from certain timing attacks against regular equality operators. ### Best Practices - **Acknowledge events immediately**. If your webhook script performs complex logic, or makes network calls, it’s possible that the script would time out before Getaround sees its complete execution. Ideally, your webhook handler code (acknowledging receipt of an event by returning a `2xx` status code) is separate of any other logic you do for that event. - **Handle duplicate events**. Webhook endpoints might occasionally receive the same event more than once. We advise you to guard against duplicated event receipts by making your event processing idempotent. One way of doing this is logging the events you’ve processed, and then not processing already-logged events. - **Do not expect events in order**. Getaround does not guarantee delivery of events in the order in which they are generated. Your endpoint should therefore handle this accordingly. We do provide an `occurred_at` timestamp for each event, though, to help reconcile ordering.

uv1.0.2