forEach, map and filter with break and return emulation
Swizzle a little something into your require() calls.
css-line-break ==============
Find the position of grapheme cluster breaks in a string
hard break extension for tiptap
PostCSS plugin postcss-page-break to fallback `break-` properties with `page-break-` alias
Page break feature for CKEditor 5.
mdast utility to support hard breaks without needing spaces or escapes
An implementation of the Unicode Line Breaking Algorithm (UAX #14)
Transform stream to read line-by-line and write a string
Bare bones Promises/A+ implementation
An optimised way to copy'ing an object. A small and simple integration
Compare, format, diff and serialize any JavaScript value
remark-lint rule to warn when too many spaces are used to create a hard break
A better forEach
High-priority task queue for Node.js and browsers
split a Text Stream into a Line Stream, using Stream 3
Nested clients for AWS SDK packages.
An implementation of the Unicode Line Breaking Algorithm (UAX #14)
Merge objects & other types recursively. A simple & small integration.
Given a response from the npm security api, render it into a variety of security reports
Add `br` tags to your editor.
A TailwindCSS plugin for breaking out of containers.
Compile component for use during server-side rendering
Break large filters into components and see how each component affects the result
Return the string broken up by newlines, so that each lines is no longer than the max lenght. Prefer to break words on spaces.
_THE GEM IS CURRENTLY IN DEVELOPMENT, IS MISSING LARGE CHUNKS OF CORE FUNCTIONALITY, AND WILL MOST CERTAINLY UNDERGO BREAKING CHANGES IN THE NEAR FUTURE. USE AT YOUR OWN RISK._ upshop tracks git commits of each theme deployment and performs differential deploys of changed files
There are 3 breaks, short, mid, and long, each with default characters and lengths. use as linebreaker.short/mid/long('string to act as header' , 'amount of separtors', 'string to separate on')
A minimal implementation of integration testing within RSpec. Allows you to build sequential specs, each with a description, but where state is maintained between tests and before/after actions are only triggered at the beginning and end of the entire sequence. Cool things you can do with this: * Build multi-step user stories in plain RSpec syntax. Locate the point of failure quickly, and break up large integrations into sensible steps * Speed up groups of related tests by running your factories only once before the whole group.
Codebreaker is a logic game in which a code-breaker tries to break a secret code created by a code-maker. The codemaker, which will be played by the application we're going to write, creates a secret code of four numbers between 1 and 6. The codebreaker gets some number of chances to break the code (depends on chosen difficulty). In each turn, the codebreaker makes a guess of 4 numbers.
Langda monitors Ruby loop operations (each, map, select, etc.), counts their iterations, measures execution time, and logs slow loops. It helps developers quickly identify performance bottlenecks in real application code with zero configuration and no breaking changes.
Administrate is heavily inspired by projects like Rails Admin and ActiveAdmin, but aims to provide a better user experience for site admins, and to be easier for developers to customize. To do that, we're following a few simple rules: - No DSLs (domain-specific languages) - Support the simplest use cases, and let the user override defaults with standard tools such as plain Rails controllers and views. - Break up the library into core components and plugins, so each component stays small and easy to maintain.
Administrate is heavily inspired by projects like Rails Admin and ActiveAdmin, but aims to provide a better user experience for site admins, and to be easier for developers to customize. To do that, we're following a few simple rules: - No DSLs (domain-specific languages) - Support the simplest use cases, and let the user override defaults with standard tools such as plain Rails controllers and views. - Break up the library into core components and plugins, so each component stays small and easy to maintain.
Helpers to read debian control files
- xcsims: Delete all simulators and recreate one for each compatible platform and device type pairing. - sync-git-remotes: Make sure all your GitHub repos are cloned into a given directory and keep them synced with upstream. Forks are maintained with a remote for both the fork and upstream, both remotes' default branches are tracked in local counterparts, and the upstream default branch is also pushed to the fork. - changetag: Extract changelog entries to write into git tag annotation messages. - prerelease-podspec: Branch and create/push a release candidate tag, modify the podspec to use that version tag, and try linting it. - release-podspec: Create a tag with the version and push it to repo origin, push podspec to CocoaPods trunk. - revert-failed-release-tag: In case `release-podspec` fails, make sure the tag it may have created/pushed is destroyed before trying to run it again after fixing, so it doesn't break due to the tag already existing the second time around. - bumpr: Increment the desired part of a version number (major/minor/patch/build) and write the change to a git commit. - clean-rc-tags: deletes any release candidate tags leftover after prerelease testing. - migrate-changelog: for a changelog adhering to [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), move any contents under Unreleased to a new section for a new version with the current date.
# Fancy Logger An easily customizable logger with style. ## Install ### Bundler: `gem 'fancy_logger'` ### RubyGems: `gem install fancy_logger` ## Usage Simply use as if you were using the normal Ruby `Logger` class: ```ruby require 'fancy_logger' logger = FancyLogger.new(STDOUT) logger.info "Hello" ``` ### Config The `config` instance method allows you to modify the configuration of the Logger within a DSL. Continuing with our last example: ```ruby logger.config do timestamp_format "%c" styles do info do foreground :yellow blink true end end end logger.debug 'Look here!' logger.info 'Doing things...' logger.warn 'Watch out!' logger.error 'Bad' logger.fatal 'VERY bad' logger.unknown 'Weird unknown stuff' ``` #### Output ![][output_example] ### Config ```ruby # The format of the timestamp in the log. Follows the strftime standards. timestamp_format "%F %r" # On the first logged message, FancyLogger will prepend a help message # containing a list of all the severities (debug, info, warn, etc) styled # according to your config as reference. # You can disable this by setting the below option to false. show_help_message true # Under styles, you have a configuration for each severity. # Each severity has a configuration with the following valid options: # Key: foreground # Value: # :default, :black, :red, :green, :yellow, :blue, :magenta, :cyan, :white # # Key: background # Value: # :default, :black, :red, :green, :yellow, :blue, :magenta, :cyan, :white # # Key: reset # Value: true or false # # Key: bright # Value: true or false # # Key: italic # Value: true or false # # Key: underline # Value: true or false # # Key: # blink # Value: true or false # # Key: inverse # Value: true or false # # Key: hide # Value: true or false styles do debug do foreground :black background :cyan end info do foreground :default background :default end warn do foreground :yellow background :default blink true end error do foreground :red background :default end fatal do foreground :black background :red bold true underline true end unknown do foreground :black background :white underline true end end ``` ## Contributing * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it * Fork the project * Start or switch to a testing/unstable/feature/bugfix branch * Commit and push until you are happy with your contribution * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally. * Please try not to mess with the Rakefile, VERSION or gemspec. ## Copyright Copyright © 2012 Ryan Scott Lewis <ryan@rynet.us>. The MIT License (MIT) - See LICENSE for further details. [output_example]: http://oi44.tinypic.com/sfwlkp.jpg