A TypeScript ORM inspired by ActiveRecord for PostgreSQL, SQLite, and (TODO: MySQL) running on Bun
Ëmber Wrapper for Video JS Record
[](https://www.npmjs.com/package/@aws-sdk/util-dynamodb) [](https://www.npmjs.com/package/@aws-sdk/util
OpenTelemetry metrics SDK
A strongly typed immutable-js record interface
This package contains all the record related code in rrweb. See the [guide](../../guide.md) for more info on rrweb.
record and replay the web
OpenTelemetry Tracing
This package contains all the record related code in rrweb. See the [guide](../../guide.md) for more info on rrweb.
Create fancy log entries for errors and function call sites.
Ultra-fast MessagePack implementation with extensions for records and structured cloning
OpenTelemetry logs SDK
Please refer to the [console recipe](../../../docs/recipes/console.md) on how to use this plugin. See the [guide](../../../guide.md) for more info on rrweb.
Used to transfer signed peer data across the network
TypeScript definitions for dom-mediacapture-record
No description provided.
Record, replay, and stub HTTP Interactions
a JSON logging library for node.js services
Create fancy log entries for errors and function call sites.
IPNS record definitions
A polyfill for the Record and Tuple Stage 2 ECMAScript proposal.
Shared utilities and constants between @pollyjs packages
Convert object keys to camel case
Extendable base persister class used by @pollyjs
Auto-syncs records in client-side JS (through a Model DSL) from changes (updates/destroy) in the backend Rails server through ActionCable. Also supports streaming newly created records to client-side JS. Supports lost connection restreaming for both new records (create), and record-changes (updates/destroy). Auto-updates DOM elements mapped to a record attribute, from changes (updates/destroy).
With minimal set up ActiveSync presents limited rails model interfaces within the JS font end. Records accessed are kept updated through action cable.
== E9Tags An extension to ActsAsTaggableOn[http://github.com/mbleigh/acts-as-taggable-on] which "improves" on custom tagging, or at least makes it more dynamic. Additionally it provides some autocomplete rack apps and the corresponding javascript. == Installation 1. E9Tags requires jquery and jquery-ui for the autocompletion and tag-adding form, be sure they're loaded in your pages where the tags form will be rendered. 2. E9Tags extends ActsAsTaggableOn and requires it. Run it's generator if you have not. 3. Run the E9Tags install script to copy over the required JS rails g e9_tags:install 4. Then make sure it is loaded, how you do that doesn't matter, e.g. <%= javascript_include_tag 'e9_tags' %> 5. Create an initializer for that sets up the taggable models and their controllers. This gives the models the tag associations and methods and prepares their controller to handle the otherwise unexpected tag params. require 'e9_tags' require 'contacts_controller' require 'contact' E9Tags.controllers << ContactsController E9Tags.models << Contact OR You can just include the modules in your classes yourself. The first way really exists for the case where the classes you wish to extend are part of another plugin/gem. # in contact.rb include E9Tags:Model # in contacts_controller.rb include E9Tags::Controller 6. Render the tags form partial in whatever model forms require it. = render 'e9_tags/form', :f => f If you pass a context, it will be locked and no longer possible to change/add the contexts on the form (and as a side effect, the tags autocompletion will be restricted to that context). = render 'e9_tags/form', :f => f, :context => :users Finally if you pass a 2nd arg to :context you can set a tag context to be "private" (default is false). In this case the tag context will be locked as private (typically suffixed with *), meaning that the tags will not be publicly searchable/visible. This is useful for organizational tags tags, say if you wanted to arbitrarily group records, or create a custom search based on a tag context. = render 'e9_tags/form', :f => f, :context => [:users, true] NOTE: The form and javascript are intended to work out of the box, but the certainly aren't going to look pretty. If you do intend to use the forms, you'll no doubt need to style them.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.