Build extensible Draft.js editors with configurable plugins and integrated serialization.
JSON Schema Draft 4 namespace for ApiDOM.
JSON Schema Draft 6 namespace for ApiDOM.
JSON Schema Draft 7 namespace for ApiDOM.
Extensibly serialize & deserialize Draft.js ContentState
Ajv class for JSON Schema draft-04
Another JSON Schema Validator
JSON Schema TypeScript definitions with complete inline documentation.
Extend an object with the properties of additional objects. node.js/javascript util.
Port of jQuery.extend for node.js and the browser
Adds a static `extend` method to a class, to simplify inheritance. Extends the static properties, prototype properties, and descriptors from a `Parent` constructor onto `Child` constructors.
Basic IP rate-limiting middleware for Express. Use to limit repeated requests to public APIs and/or endpoints such as password reset.
TypeScript definitions for draft-js
Another JSON Schema Validator
extend an object
Editor for DraftJS Plugins
Customizable and hackable json-validator and json-schema utilities for traversal, data generation and validation
A wysiwyg on top of DraftJS.
Migrate JSON-Schema to draft-06
Fast, lightweight JSON Schema validator for Node.js and browsers — full support for draft-04, draft-06, draft-07, draft-2019-09, and draft-2020-12 (latest)
A React framework for building text editors.
Collection of utility function for use with Draftjs.
Reusable JSON Schema (Draft 04) validation library for Expo
Recursive object extending
SimpleHKP is a simple Ruby/rack based GnuPG extendedHKP key and identity server packaged as a standard Ruby Gem. As such it conforms to an {extended version}[http://stephengaito.github.io/rGem-simple-gnupg-keyserver/] of {the OpenPGP HTTP Keyserver Protocol (HKP) (draft-shaw-openpgp-hkp-00.txt)}[http://tools.ietf.org/html/draft-shaw-openpgp-hkp-00]. The {associated documentation}[https://stephengaito.github.io/rGem-simple-gnupg-keyserver] provides more detail.
A consolidated Rails engine gem that extends Mastodon with Newsmast features: custom registration flows, push notifications, content filtering, custom feeds, draft management, ALT text generation, local-only posts, and extended timelines.
## A mirror API for Ruby In various [research][p1] [projects][p2] the advantages of having a [mirror API][p3] to separate reflection from a language implementation have been discussed, and "industry grade" implementations exist for [Java][p4] and [C#][p5]. This project aims at providing a number of specs and classes that document a mirror API for Ruby. The mirror implementation that is part of this project will use only those language facilities that are available across Ruby implementations. The specs, however, will also test behavior that cannot be provided in such a manner. The idea here is that in time, all implementations provide their own implementation of the mirror API, and all implementations collaborate on this one spec. Why do this, you ask? Because Ruby needs tools, and those tools need to be written in Ruby. If they are not, then people will be excluded from tinkering with their tools, thus impeding innovation. You only have to look at Emacs or Smalltalk to see what's possible when programmers can extend their tools, all tools, in a language they feel comfortable in. If we have a standard mirror API, all tools that are written **for** Ruby, **in** Ruby, can be shared across implementations, while at the same time allowing language implementers to use the facilities of their platform to provide optimal reflective capabilities without tying them to internals. [p1]: http://www.cs.virginia.edu/~lorenz/papers/icse03/icse2003.pdf "Pluggable Reflection: Decoupling Meta-Interface and Implementation" [p2]: http://bracha.org/newspeak-spec.pdf "Newspeak Programming Language Draft Specification, Version 0.06, pages 40 onward" [p3]: http://www.hpi.uni-potsdam.de/hirschfeld/events/past/media/100105_Bracha_2010_LinguisticReflectionViaMirrors_HPI.mp4 "Linguistic Reflection Via Mirrors" [p4]: http://bracha.org/mirrors.pdf "Mirrors: Design Principles for Meta-level Facilities of Object-Oriented Programming Languages" [p5]: http://oreilly.com/catalog/progcsharp/chapter/ch18.html "See esp. 18-3, highlighting how C# reflection works on assembly rather than VM objects"
No description provided.
No description provided.
No description provided.
No description provided.