Spec Core Library
Core Library for Elm-Spec Runners
Core types and rendering for usage spec
JSON Schema validation and specifications
No description provided.
Shared generic JSON RPC specifications
Simple menu elements for ProseMirror
Parser adapter for parsing JSON documents into AsyncAPI 2.x.y namespace.
Parser adapter for parsing YAML documents into AsyncAPI 2.x.y namespace.
AsyncAPI 2.x.y namespace for ApiDOM.
EditorConfig File Locator and Interpreter for Node.js
Core parser library to generate apidoc result following the apidoc-spec
YAML parser and field state resolver for Open Form Spec
A Babel plugin to inject imports to core-js@3 polyfills
A spec-compliant client-side GraphQL implementation
JSON becomes real things. Define your catalog, register your components, let AI generate.
Shared TypeScript types and reporter contracts for the ACT v0.1 reference implementation. Types are derived from schemas/ via codegen.
Actions core lib
Schema-driven relayfile adapter generator and runtime
Library of JavaScript stage-0 decorators (aka ES2016/ES7 decorators but that's not accurate!) inspired by languages that come with built-ins like @override, @deprecate, @autobind, @mixin and more! Works great with React/Angular/more!
Types and schema that specs of the Markup languages for markuplint
Core Promise support implementation for the simplified HTTP request client 'request'.
A terminating Apollo Link for Apollo Client that fetches a GraphQL multipart request if the GraphQL variables contain files (by default FileList, File, or Blob instances), or else fetches a regular GraphQL POST or GET request (depending on the config and
Use react-devtools outside of the browser
Core library for parsing and generating Rust code from .unit.spec files
Core library for generating OpenAPI specifications from tests
Core event types and traits for DocSpec streaming document conversion
Core analysis engine for exspec
Formspec core processing — FEL analysis, path utils, schema validation, assembler
Core library for lintspec
Core types and validation for PlanSpec declarative work orchestration
See http://www.openannotation.org/spec/core/
Wrapper class for RDF::Graph that adds methods specific to OpenAnnotation graphs. http://www.openannotation.org/spec/core/
OpenGL core profile (3.2 onward, no deprecated functionality) bindings for Ruby 2.x. Generated from Khronos XML spec files.
A Rubygems remote source server that implements the core Rubygems web API (gem indicies, specs, push, and yank). Wins for local and private gem servers.
Core module for EdgeBase Ruby SDK. Provides HttpClient, TableRef, DocRef, StorageClient, and generated API layer from OpenAPI spec.
The Screw Unit server conveniently serves your Screw Unit specs and implementations javascript files and css stylesheets. The Screw Unit core is located at http://github.com/nkallen/screw-unit/tree.
This gem is a logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/plugin install gemname. This gem is not a stand-alone program. The aim is to parse non standard serialization format, see spec for format descitpion
# Studio Game Studio Game is a Ruby-based project that demonstrates object-oriented programming concepts. It includes classes and modules to manage players, games, and scoring. ## Project Structure - `lib/`: Contains the core Ruby files for the game logic. - `game.rb`: Defines the main game class. - `player.rb`: Manages player attributes and behaviors. - `treasure_trove.rb`: Handles treasures and their values. - `bin/`: Contains executable scripts to run the game. - `studio_game`: The main entry point to start the game. - `spec/`: Contains unit tests for the game. - `game_spec.rb`: Tests for the game class. - `player_spec.rb`: Tests for the player class. - `README.md`: Project documentation. - `LICENSE`: MIT License file. ## How to Run 1. Clone the repository. 2. Navigate to the `studio_game` directory. 3. Run the game using: ```bash ruby bin/studio_game ``` ## Testing To ensure the game logic works as expected, run the unit tests included in the `spec/` directory. Use the following command: ```bash rspec spec/ ``` This will execute all the test files and display the results in the terminal.
= dm-is-published This plugin makes it very easy to add different states to your models, like 'draft' vs 'live'. By default it also adds validations of the field value. Originally inspired by the Rails plugin +acts_as_publishable+ by <b>fr.ivolo.us</b>. == Installation # Add GitHub to your RubyGems sources $ gem sources -a http://gems.github.com $ (sudo)? gem install kematzy-dm-is-published <b>NB! Depends upon the whole DataMapper suite being installed, and has ONLY been tested with DM 0.10.0 (next branch).</b> == Getting Started First of all, for a better understanding of this gem, make sure you study the '<tt>dm-is-published/spec/integration/published_spec.rb</tt>' file. ---- Require +dm-is-published+ in your app. require 'dm-core' # must be required first require 'dm-is-published' Lets say we have an Article class, and each Article can have a current state, ie: whether it's Live, Draft or an Obituary awaiting the death of someone famous (real or rumored) class Article include DataMapper::Resource property :id, Serial property :title, String ...<snip> is :published end Once you have your Article model we can create our Articles just as normal Article.create(:title => 'Example 1') The instance of <tt>Article.get(1)</tt> now has the following things for free: * a <tt>:publish_status</tt> attribute with the value <tt>'live'</tt>. Default choices are <tt>[ :live, :draft, :hidden ]</tt>. * <tt>:is_live?, :is_draft? or :is_hidden?</tt> methods that returns true/false based upon the state. * <tt>:save_as_live</tt>, <tt>:save_as_draft</tt> or <tt>:save_as_hidden</tt> converts the instance to the state and saves it. * <tt>:publishable?</tt> method that returns true for models where <tt>is :published </tt> has been declared, but <b>false</b> for those where it has not been declared. The Article class also gets a bit of new functionality: Article.all(:draft) => finds all Articles with :publish_status = :draft Article.all(:draft, :author => @author_joe ) => finds all Articles with :publish_status = :draft and author == Joe Todo Need to write more documentation here.. == Usage Scenarios In a Blog/Publishing scenario you could use it like this: class Article ...<snip>... is :published :live, :draft, :hidden end Whereas in another scenario - like in a MenuItem model for a Restaurant - you could use it like this: class MenuItem ...<snip>... is :published :on, :off # the item is either on the menu or not end == RTFM As I said above, for a better understanding of this gem/plugin, make sure you study the '<tt>dm-is-published/spec/integration/published_spec.rb</tt>' file. == Errors / Bugs If something is not behaving intuitively, it is a bug, and should be reported. Report it here: http://github.com/kematzy/dm-is-published/issues == Credits Copyright (c) 2009-07-11 [kematzy gmail com] Loosely based on the ActsAsPublishable plugin by [http://fr.ivolo.us/posts/acts-as-publishable] == Licence Released under the MIT license.
Contentful API wrapper library exposing an ActiveRecord-like interface
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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.