ONES Design Coverage Report Action
Analyzes sketch files to determine usage of external libraries (e.g. a design system).
Project audit — token usage, contrast, motion, accessibility, design coverage, responsive layout.
Security-by-design coverage reporters for Vitest with built-in PII anonymization
A cssinjs util library to support Ant Design (antd) and its ecosystem libraries.
fast and small color class
A inter-process and inter-machine lockfile utility that works on a local or network file system
An ESLint plugin that enforces the use of import aliases. Also supports autofixing.
Provides a regex that can be used to test if a string is a valid NPM package name.
Helper functions for V8 coverage files.
css-in-js solution for application combine with antd v5 token system and emotion
Patch for antd v5 to support React 19
Utilities for ESLint plugins.
Use this module to start and stop the V8 inspector manually and collect precise coverage.
Data library for istanbul coverage objects
V8 coverage provider for Vitest
Color palettes calculator of Ant Design
A module for detecting and responding to the user becoming idle in Angular applications.
<!-- TITLE/ --> # @dword-design/defaults <!-- /TITLE -->
TypeScript definitions for istanbul-lib-coverage
Simply swizzle your arguments
No description provided.
An enterprise-class UI design language and React components implementation
Module that works with @ng-idle/core to keep a user session alive while user is active.
swagger_coverage programmatically compares Swagger API routes to existing routes from the source code and reports the difference(s)
cover_rage is a Ruby code coverage tool designed to be simple and easy to use. It can be used not only for test coverage but also in production services to identify unused code. Key features: 1. Runs in continuous processes (e.g., Rails servers) 2. Zero dependencies 3. Supports forking and daemonization without additional setup
This gem is designed to fail in the face of anti-virus coverage of your gem path. If you are running anti-virus systemwide, this gem will not load since it will be deleted or quarantined.
Evilution is a mutation testing tool for Ruby. It validates test suite quality by making small code changes and checking if tests catch them. AI-agent-first design with JSON output, diff-based targeting, and coverage-based filtering.
Following TDD practice, designed with few useful patterns, styled with rubocop style guide, documented with yard convention, lines of code analysis, 100% tests coverage and properly error handled rubygem project could be very useful to assess one's knowledge in build rubygems.
Models, Controllers, and Views common to Watermark Church apps
# XQuery [](https://gitter.im/JelF/xquery?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) [](https://travis-ci.org/JelF/xquery) [](https://codeclimate.com/github/JelF/xquery) [](https://codeclimate.com/github/JelF/xquery/coverage) [](https://codeclimate.com/github/JelF/xquery) XQuery is designed to replace boring method call chains and allow to easier convert it in a builder classes ## Usage of `XQuery` function `XQuery` is a shortcat to `XQuery::Generic.with` ``` r = XQuery(''.html_safe) do |q| # similar to tap q << 'bla bla bla' q << 'bla bla bla' # using truncate q.truncate(15) # real content (q.send(:query)) mutated q << '!' end r # => "bla bla blab...!" ``` ## Usage of `XQuery::Abstract` I designed this gem to help me with `ActiveRecord` Queries, so i inherited `XQuery::Abstract` and used it's powers. It provides the following features ### `wrap_method` and `wrap_methods` when you call each of this methods they became automatically wrapped (`XQuery::Abstract` basically wraps all methods query `#respond_to?`) It means, that there are instance methods with same name defined and will change a `#query` to their call result. ``` self.query = query.foo(x) # is basically the same as foo(x) # when `wrap_method :foo` called ``` You can also specify new name using `wrap_method :foo, as: :bar` syntax ### `q` object `q` is a proxy object which holds all of wrapped methods, but not methods you defined inside your class. E.g. i have defined `wrap_method(:foo)`, but also delegated `#foo` to some another object. If i call `q.foo`, i will get wrapped method. Note, that if you redefine `#__foo` method, q.foo will call it instead of normal work. You can add additional methods to `q` using something like `alias_on_q :foo`. I used it with `kaminary` and it was useful ``` def page=(x) apply { |query| query.page(x) } end alias_on_q :page= def page query.current_page end alias_on_q :page ``` ### `query_superclass` You should specify `query_superclass` class_attribute to inherit `XQuery::Abstract`. Whenever `query.is_a?(query_superclass)` evaluate to false, you will get `XQuery::QuerySuperclassChanged` exception. It can save you much time when your class misconfigured. E.g. you are using `select!` and it returns `nil`, because why not? ### `#apply` method `#apply` does exact what it source tells ``` # yields query inside block # @param block [#to_proc] # @return [XQuery::Abstract] self def apply(&block) self.query = block.call(query) self end ``` It is usefull to merge different queries. ### `with` class method You can get XQuery functionality even you have not defined a specific class (You are still have to inherit XQuery::Abstract to use it) You can see it in this document when i described `XQuery` function. Note, that it yields a class instance, not `q` object. It accepts any arguments, they will be passed to a constructor (except block) ### `execute` method Preferred way to call public instance methods. Resulting query would be returned
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.