Results for hooks-as-store

Use React custom hooks in Svelte Apps.

Hooks as store

Backwards compatible shim for React's useSyncExternalStore. Works with any React that supports hooks.

Simple key-value storage with support for multiple backends

Core Inquirer prompt API

A WebdriverIO service to exchange data across processes

[](https://github.com/100mslive/web-sdks/actions/workflows/lint-test-build.yml) [![Bundle Size](https://badgen.net/bundlephobia/minzip/@100mslive

Relay Hooks

A modular store factory using zustand

Jotai store factory for a best-in-class developer experience.

Event Emitting and Middleware Hooks

Next-generation take on pre/post function hooks

Just a little module for plugins.

the complete solution for node.js command-line programs

CJS and ESM hooks for orchestrion

Airbnb's ESLint config, following our styleguide

ESLint rules for React Hooks

A mock store for testing your redux async action creators and middleware

Welcome to the README of Gurx, an typescript-native reactive state management library for complex web applications and components that do not have the symmetry of the store object and the component tree.

detector of copy/paste in files

PocketBase JavaScript SDK

WordPress hooks library.

List of Git hooks

Simple and complete React hooks testing utilities that encourage good testing practices.

Set of git hooks to store YAML files instead of Xcode projects and nibs in repo

It stores git hooks and force git hooks installation.

= RUGS - RUby Git Setup A helper script that makes setting up remote git repositories a snap. == WARNING: This is still alpha so use it at your own risk! Note: I don't use alpha/beta in the version numbers until I have a first real release because of how Ruby Gems handles them. == What is it? RUGS has three main functions: * Creates a local git repository and directory structure using default templates or ones you create. * Sets up a remote repository to mirror your local one. * Adds a framework of git hooks allowing you to store and run your own hooks in directly from the repo. RUGS makes creating remote repos as simple as `rugs create repo_name on server_name`. RUGS even allows you to automatically embed your Git hooks in the repo itself. No more jumping through hoops to make sure your hooks are maintained with your project; with RUGS you just store your hook scripts in the `git_hooks` directory and they're automatically updated and run. \ Once you've set up your project using RUGS you just use Git as you normally would with the exception of your hooks being the in `git_hooks` directory.

This plugin creates a Value Object class that controls the logic of incomplete dates. It also creates a class method incomplete_date_attr to hook onto Active Record objects, so some of the attributes are stored in the database as an integer instead of a date

Validating-Workflow is a finite-state-machine-inspired API for modeling and interacting with what we tend to refer to as 'workflow'. * nice DSL to describe your states, events and transitions * robust integration with ActiveRecord and non relational data stores * various hooks for single transitions, entering state etc. * convenient access to the workflow specification: list states, possible events for particular state * state and transition dependent validations for ActiveModel

Workflow is a finite-state-machine-inspired API for modeling and interacting with what we tend to refer to as 'workflow'. * nice DSL to describe your states, events and transitions * robust integration with ActiveRecord and non relational data stores * various hooks for single transitions, entering state etc. * convenient access to the workflow specification: list states, possible events for particular state

Workflow is a finite-state-machine-inspired API for modeling and interacting with what we tend to refer to as 'workflow'. * nice DSL to describe your states, events and transitions * robust integration with ActiveRecord and non relational data stores * various hooks for single transitions, entering state etc. * convenient access to the workflow specification: list states, possible events for particular state

Workflow is a finite-state-machine-inspired API for modeling and interacting with what we tend to refer to as 'workflow'. * nice DSL to describe your states, events and transitions * robust integration with ActiveRecord and non relational data stores * various hooks for single transitions, entering state etc. * convenient access to the workflow specification: list states, possible events for particular state Temporary version to address possible rails4 issues

Opinionated local CI that checks your code before it leaves your machine. Runs a four-stage pipeline (lint, build, fast tests, slow tests) on every commit with strict time budgets. Hooks into git pre-commit and pre-push, stores results in SQLite, and includes a TUI dashboard for monitoring.

Dead Simple CMS is a library for modifying different parts of your website without the overhead of having a fullblown CMS. The idea with this library is simple: provide an easy way to hook into different parts of your application (not only views) by defining the different parts to modify in an easy, straight-forward DSL. The basic components of this library include: * A DSL to define the changeable values in your app * Form generators based on SimpleForm (with or without Bootstrap) and default rails FormBuilder * Expandable storage mechanisms so you can store the data in different locations * Currently supported: Redis, Database, Memcache, even Memory (for testing) * Presenters/renderers so you can take groups of variables and render them into your views (ie image_tag) What it doesn't have: * Versioning - be able to look at old versions of the content * Timing - set start and end time for different content * Page builder tools - this is not the right tool if you want to design full pages

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.