hierarchical RESTful routes utility
Cross Platform implementation of the GitLab API
Document Intelligence Rest Client
Compile object rest and spread to ES5
Allow parsing of object rest/spread
Octokit plugin adding one method for all of api.github.com REST API endpoints
TypeScript definitions for arcgis-rest-api
Workaround a Safari bug where rest destructuring with an array literal on the rhs can yield incorrect results
unist utility to find a node after another node
Microsoft Azure Storage SDK for JavaScript - Blob
An isomorphic client library for the Azure Translator Service
Core API implementation of the GitLab API
REST DataSource for Apollo Server v4
Extendable client for GitHub's REST & GraphQL APIs
Shared TypeScript definitions for Octokit projects
Webpack loader for Sucrase
Node Rest and Http Clients for use with TypeScript
An HTTP/REST based Redis client built on top of Upstash REST API.
Voice Error Codes
TypeScript definitions for @woocommerce/woocommerce-rest-api
GitHub REST API client for Node.js
Inference API for Azure-supported AI models
Octokit plugin to paginate REST API endpoint responses
Azure DevOps backend for Decap CMS
Generic endpoints and specific implementations.
Provides tree-based routing syntax for building RESTful APIs.
A ruby gem for active record which simplify the copy of very complex tree data.
Hammock is a Rails plugin that eliminates redundant code in a very RESTful manner. It does this in lots in lots of different places, but in one manner: it encourages specification in place of implementation. Hammock enforces RESTful resource access by abstracting actions away from the controller in favour of a clean, model-like callback system. Hammock tackles the hard and soft sides of security at once with a scoping security system on your models. Specify who can verb what resources under what conditions once, and everything else - the actual security, link generation, index filtering - just happens. Hammock inspects your routes and resources to generate a routing tree for each resource. Parent resources in a nested route are handled transparently at every point - record retrieval, creation, and linking. It makes more sense when you see how it works though. There's a screencast coming soon.
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.