Promised help is a series of helpers for native es6 promises
TypeScript definitions for chai-as-promised
Retry a failed promise
Some awesome description
A generic promised based retry mechanism. Useful for eg. ensuring an available database or message queue connection
Promise-based IO
Wrapper for Handlebars that allows helpers returning promises
For limiting the time to resolve a promise.
Sugar methods for using sinon.js stubs with promises
A WebSocket client library providing Promise-based API for connecting, disconnecting and messaging with server
TypeScript definitions for supertest-as-promised
@idxdb/promised wraps the IndexedDB API. It allows you to easily store and retrieve data in an indexed db database using async/await syntax, making it easier to integrate with your existing codebase.
Turns a function into one that always returns a Promise a la Blubird's Promise.method.
A map of promises that can be resolved or rejected by key
Prevent common problems when using chai-as-promised
Chai-as-promised plugin for karma
Extends Chai with assertions about promises.
Alternate Promise.race() implementation which doesn't leak memory, courtesy Brian Kim (https://github.com/brainkim)
A minimalistic finite state machine library using promises
SuperAgent with a Promise twist
Extends Chai with assertions about promises.
Kris Zyp's implementation of promises with added features, maintained as an npm package.
A wrapper arround sqlite3 node.js package to use promise
Convert all soap methods to promises. Inspired by soap-q.
When you write a web API, you make a promise to the world. RSpec API helps you keep your promise.
Sometimes we have to write some Rails code in the migrations and it's hard to keep them in working state because models wich are used there changes too often. there some techniques which help to avoid these pitfalls. For example, define model classes in the migrations or write raw SQL. But they don't help in 100% cases anyway. This gem promises to solve the problem in a simple way.
Interactors are a pattern for structuring your business logic into units. They have a flexible context that they pass between them, which makes them easy-to-write, but hard-to-understand after you've written them. Much of this confusion comes from not knowing what the interactor is supposed to take as input and what it's expected to produce. Enter contracts. Contracts allow you define, up front, a contract both for the input of an interactor, known as expectations, and the output of it, known as promises. Additionally, you can define a handler for what happens when an interactor violates its contracts, known as a breach. Declaring these contracts can help define your interface and make it easier to understand how to use an interactor. They form both documentation and validation for your business logic.
Wish you could write your Ruby in XML? Has the fact that Ruby is not "enterprise" got you down? Do you feel like your Ruby code could be made to be more "scalable"? Well look no further my friend. You've found the enterprise gem. Once you install this gem, you too can make Rails scale, Ruby faster, your code more attractive, *and* have more XML in your life. I'm sure you're asking yourself, "how can the enterprise gem promise so much?". Well the answer is easy, through the magic of XML! The enterprise gem allows you to write your Ruby code in XML, therefore making your Ruby and Rails code scale. Benefits of writing your code in XML include: * It's easy to read! * It scales! * Cross platform * TRANSFORM! your code using XSLT! * Search your AST with XPath *or* CSS! The enterprise gem even comes with a handy "enterprise" binary to help you start converting your existing *legacy* Ruby code in to scaleable, easy to read XML files. Let's start getting rid of that nasty Ruby code and replacing it with XML today!