Auto generate form elements and validation
Jupyter interactive widgets
A set of core FlexDash widgets for Node-RED.
Schemas for the Jupyter interactive Widgets
UI widgets for deck.gl
A suite of React components providing functionality for enterprise app workflows.
A widgets library for use with CesiumJS. CesiumJS is a JavaScript library for creating 3D globes and 2D maps in a web browser without a plugin.
A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.
Build dashboards (or any other application) using ascii/ansi art and javascript.
a 'json' command for massaging and processing JSON on the command line
InstantSearch.css is a CSS library to style InstantSearch-powered search experiences.
Node-RED nodes for the FlexDash dashboard
Matrix Widget API SDK
Angular powered Bootstrap
A Vue 3 component library for building node-graph editors. Ships a graph editor component, a type/coalescer system with multi-hop conversion, and a JSON AST output suitable for shader codegen.
An à la carte set of polished, extensible, and accessible inputs built for React
SVAR React Core library is a collection of customizable React UI components and form controls
FusionCharts JavaScript charting framework
Adds widgets for Builder.io editing, such as carousels, tabs, accordions, etc.
Widgets.
Analyze the exported API for a TypeScript library and generate reviews, documentation, and .d.ts rollups
Wrap a controlled react component, to allow specific prop/handler pairs to be uncontrolled
Twitter widgets as React components
Functionality used by the widgets block editor in the Widgets screen and the Customizer.
Enriches Inquirex flow definitions with framework-agnostic widget rendering metadata. Adds `widget` and `widget_mobile` DSL verbs that attach WidgetHint objects to nodes. Consumed by inquirex-tty, inquirex-js, and inquirex-rails adapters. Produces enriched JSON — no HTML or JavaScript generated.
# Chef Data Region ## Description Chef Data Region extends the `Chef::DSL::DataQuery` module's `data_bag_item` method with the ability to dynamically expand the data bag name in a configurable, environment-specific manner. ## Motivation This gem exists to address the following scenario: An organization maintains data in Chef data bag items. The data is deployed to several data center environments and is stored in data bags whose names reference the environments. The organization wants to write environment-agnostic recipes that access the data bags without explicitly referencing the data bags by their environment names. As a concrete example, imagine the organization maintains encrypted data for three deployment environments: development, staging, and production. It maintains this data in three data bags, one for each environment, with data for services named `gadget` and `widget` in items: | Environment | Bag | Item | |-------------+----------------+--------| | Development | secure-dev | gadget | | Development | secure-dev | widget | | Production | secure-prod | gadget | | Production | secure-prod | widget | | Staging | secure-staging | gadget | | Staging | secure-staging | widget | The items are encrypted with a key unique to that environment to maximize security. Now consider how a recipe would access these bags. When then recipe is running, it needs to know the data center environment in order to construct the bag name. The organization would most likely assign the enviroment name to a node attribute. In a naive implementation, each recipe would include logic that examined the attribute's value to determine which bag to load. This would obviously duplicate code. Imagine instead that the organization wants to reference the bag by the name `secure` and rely on an _abstraction_ to translate `secure` into the environment-specific bag name. This gem provides that abstraction. ## Features This gem overrides the `data_bag_item` method with configurable logic that dynamically decides which bag to load. It retains API compatibility with `Chef::DSL::DataQuery#data_bag_item`, so existing recipes that call `data_bag_item` work without modification. The gem imposes no constraints on data bag item structure. ## Configuration Assign the region name to a node attribute that varies by environment: node.default['local'][region'] = 'staging' Add the following configuration to Chef Client's `client.rb` file. * Require the gem: require 'chef/data_region' * Configure the gem with a hash that maps a bag name to an expansion pattern: Chef::DataRegion.add( 'secure', { attribute: %w(local region), pattern: 'secure-%<attribute>s' } ) ## Bag name expansion The gem expands bag names using Ruby's `format` method. _More pending..._
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.