Collect [optionally unique] objects over a period of time and then act on them
No description provided.
No description provided.
A react component toolset for managing animations
<img src="https://react-resizable-panels.vercel.app/og.png" alt="react-resizable-panels logo" width="400" height="210" />
TypeScript definitions for react-transition-group
Implementation of the various Ethereum Transaction Types
Helpers for creating and serializing transactions
Utilities for decoding and encoding Ethereum transaction for ethers.
Helpers for creating transaction messages
The string_decoder module from Node core
visx group
Helpers for confirming Solana transactions
[](https://github.com/bitcoinjs/bip174/actions/workflows/main_ci.yml) [](https://www.npmjs.org/package/bip174)
mjml-group
Arweave JS client library
Core logic for the radio group widget implemented as a state machine
Core logic for the rating-group widget implemented as a state machine
A transaction factory implementation relying on Solana's web3.js
Helpers for creating transaction instructions
Stores transactions alongside their periodically updated statuses and manages interactions such as approval and cancellation
Node.js body parsing middleware
SPL Token Group Interface JS API
Fork of bip174 with BitGo specific changes
Create factory objects in before-all blocks for fixture-like performance
Grouping multiple DB operations in a single transaction. 100% Inspired by Ecto
Create, update, and delete records within a block, assign the same request_uuid to them, and be able to easily view and undo them
Tiny datastore library for Google App Engine with JRuby
Audit model events like update/create/delete + attribute changes + group them by transaction, in normalized table layout for easy query access.
Transaction::Simple provides a generic way to add active transaction support to objects. The transaction methods added by this module will work with most objects, excluding those that cannot be Marshal-ed (bindings, procedure objects, IO instances, or singleton objects). The transactions supported by Transaction::Simple are not associated with any sort of data store. They are "live" transactions occurring in memory on the object itself. This is to allow "test" changes to be made to an object before making the changes permanent. Transaction::Simple can handle an "infinite" number of transaction levels (limited only by memory). If I open two transactions, commit the second, but abort the first, the object will revert to the original version. Transaction::Simple supports "named" transactions, so that multiple levels of transactions can be committed, aborted, or rewound by referring to the appropriate name of the transaction. Names may be any object except nil. Transaction groups are also supported. A transaction group is an object wrapper that manages a group of objects as if they were a single object for the purpose of transaction management. All transactions for this group of objects should be performed against the transaction group object, not against individual objects in the group. Version 1.4.0 of Transaction::Simple adds a new post-rewind hook so that complex graph objects of the type in tests/tc_broken_graph.rb can correct themselves. Version 1.4.0.1 just fixes a simple bug with #transaction method handling during the deprecation warning. Version 1.4.0.2 is a small update for people who use Transaction::Simple in bundler (adding lib/transaction-simple.rb) and other scenarios where having Hoe as a runtime dependency (a bug fixed in Hoe several years ago, but not visible in Transaction::Simple because it has not needed a re-release). All of the files internally have also been marked as UTF-8, ensuring full Ruby 1.9 compatibility.
group Rails log by Web transaction or any other grouping
A library for creating commands can be done and undone. Multiple commands can be grouped together in a transaction making sure all commands succeed or gets rolled back. This gem includes a few commands for file operations but it makes it easy to create custom commands and use them for more than just file operations.
Provenance records user actions and ActiveRecord model changes in Rails applications. It groups changes per request and transaction, sanitizes sensitive data, tracks bulk operations and has_and_belongs_to_many changes, and ships structured audit events to any sink through configurable hooks.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.