Git-first task orchestrator for Spec Kit workspaces
Generate [HTTP Archive (HAR)](http://www.softwareishard.com/blog/har-12-spec/) while running tests
Token-Oriented Object Notation (TOON) – Compact, human-readable, schema-aware encoding of JSON for LLM prompts
Typings for the Figma REST API
A list of CSS features and their positions in the process of becoming implemented web standards
## What is it?
Spec-compliant FormData implementation for Node.js
Spec reporter for jasmine behavior-driven development framework
A spec-compliant client-side GraphQL implementation
A WebdriverIO plugin to report in spec style
Flow types for the Flow-ESTree spec produced by the hermes parser
Node CLI for Elm-Spec
AsyncAPI 2.x.y namespace for ApiDOM.
Parser adapter for parsing JSON documents into AsyncAPI 2.x.y namespace.
Computes specs to re-run when files change
Parser adapter for parsing YAML documents into AsyncAPI 2.x.y namespace.
Specification for jsii assemblies
A JSON schema validator that will run on Cloudflare workers. Supports drafts 4, 7, 2019-09, and 2020-12.
Parse the things that can be arguments to `npm install`
A small, fast, and correct TOML parser/serializer
programmatic library for `npm access` commands
Better TOML parsing and stringifying all in that familiar JSON interface.
Shared generic JSON RPC specifications
TypeScript definitions of Kubernetes resource types
Your favourite aging meme is reheated as an RSpec custom formatter. For entertainment purposes only. WARNING: enterprise-ready
An RSpec2 formatter that uses your iTerm2 tabs' color and titles to inform you of your spec status.
Rspec::RoarMatchers is a collection of matchers designed to enforce a contract between your spec and representer.
Don't write specs anymore, just save 'em while testing your code interactively. Specs will become a byproduct.
Use your OpenAPI3 schema to automatically perform contract testing while you write request specs
The 'propel' script helps you to push your code to a remote server while following Continuous Integration (CI) best practices. Propel first checks the CI server to make sure it's passing, and then runs the local spec suite and pushes changes. If the remote server is failing, just have propel wait for it to pass while you get a coffee.
## 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"
Contentful API wrapper library exposing an ActiveRecord-like interface
No description provided.
No description provided.
No description provided.