Google TypeScript Style
Tooling support for gjs and gts component authoring
GTS UI component library
This is the eslint parser for ember's gjs and gts files (using `<template>`), and also for Handlebars (`.hbs`) template files.
Utilities for handling *.{gjs,gts} files
Design system for gts projects
ESTree generator for gjs and gts file used by ember
GTS UI component library
html-validate transformer for Ember .gts (Glimmer) templates
TypeScript library for working with GTS (Global Type System) identifiers and JSON/JSON Schema artifacts
[![NPM Version][npm-image]][npm-url] [![TypeScript Style Guide][gts-image]][gts-url]
This is a CodeMirror 6 plugin that adds support for Glimmer (gjs and gts).
[![NPM Version][npm-image]][npm-url] [![TypeScript Style Guide][gts-image]][gts-url]
This is a CodeMirror 6 plugin that adds support for Glimmer (gjs and gts).
[![NPM Version][npm-image]][npm-url] [![GitHub Actions][github-image]][github-url] [![TypeScript Style Guide][gts-image]][gts-url]
[![NPM Version][npm-image]][npm-url] [![GitHub Actions][github-image]][github-url] [![codecov][codecov-image]][codecov-url] [![TypeScript Style Guide][gts-image]][gts-url]
[![NPM Version][npm-image]][npm-url] [![GitHub Actions][github-image]][github-url] [![TypeScript Style Guide][gts-image]][gts-url]
[![NPM Version][npm-image]][npm-url] [![GitHub Actions][github-image]][github-url] [![TypeScript Style Guide][gts-image]][gts-url]
GEOGATE-geojson handles AIS/NMEA encoding/decoding for GEOgate GPS/AIS/GTS framework
VitePress plugin for live, interactive Ember components in your documentation — write .gjs/.gts in markdown and see them render
gts 手环
This is a utility package that allows a shared a set of eslint rules - javascript and typescript - that extend [gts](https://github.com/google/gts).
GEOGATE-geojson handles AIS/NMEA encoding/decoding for GEOgate GPS/AIS/GTS framework
zmod parser adapter for Ember's .gjs and .gts files via ember-estree
Global Type System (GTS) library for Rust
Procedural macros for GTS schema generation
GTS ID validation and parsing primitives
GTS identifier validator for documentation and configuration files
SDK for types-registry module: API trait, GTS entity types, and error definitions
Gts logger
Gts transport
Types Registry module: GTS entity registration, storage, and REST API
AuthN resolver module - discovers and routes to plugins
AuthZ resolver module - discovers and routes to plugins
Resource Group module: hierarchical resource group management with GTS type system
Tenant resolver module - discovers and routes to plugins
GPS Tracking Server
Uses JSON, Nokogiri and CodeRay to highlight and prettify JSON, XML, HTML, Ruby and anything else CodeRay supports!
A pure Ruby interface to the PostgreSQL (>= 7.4) database
Speed up your test workflow: fail -> pry -> pass
Zencoder <http://zencoder.com> integration library.
Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.
email => http post
A Kafka (http://kafka.apache.org/) producer and consumer
Fluxxor is a set of Flux architecture tools for React. This gem makes it available for the Rails asset pipeline.
Uses weasyprint to create PDFs using HTML
ANSI escape code parsing library and ANSI -> HTML converter
Ansible is a fast (somewhat rough) conversion tool that takes a string with ANSI escapes and produces HTML.
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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.