Method chain as an object
draw call chain api
Toolkit of crossing chain from Call chain to SWTC chain
Functions call chain factory
MCP Server for code intelligence capabilities (Embedding, Graph-RAG, Call-chain tracing, Bug locator)
A simple asynchronous tool
API for combining call site modifiers
A hook to make async call chain in a task npm peasy.
Light client that connects to Polkadot and Substrate-based blockchains
Microservice architecture of process gateway, referred to as `MAPG`. It can drive services to dynamically create ancillary process services, manage the whole life cycle of the process tree, provide a complete micro-service call chain, support `HTTP` `TCP`
chain a bunch of functions together into a single call
Chain functions, generators, Node streams, and Web streams into a pipeline with backpressure support.
HANDLE CONFIGURATION ONCE AND FOR ALL
An easy way to set and cache context changes for Apollo Link
A utility for managing a prototype chain
Simple module to split a single certificate authority chain file (aka: bundle, ca-bundle, ca-chain, etc.) into an array, as expected by the node.js tls api.
No description provided.
TypeScript definitions for stream-chain
A logger that makes use of continuation-local-storage (cls) to record logs with the same sessionId throughout the function call chain including callbacks and event emitter handlers.
A module that glues pump and bubble-stream-error to make things easier when your public API returns a stream.
A very strict and proper argument parser.
Light client that connects to Polkadot and Substrate-based blockchains
A chaining API like webpack-chain but for markdown-it.
The Aikido Safe Chain wraps around the [npm cli](https://github.com/npm/cli), [npx](https://github.com/npm/cli/blob/latest/docs/content/commands/npx.md), [yarn](https://yarnpkg.com/), [pnpm](https://pnpm.io/), [pnpx](https://pnpm.io/cli/dlx), [rush](https
Rust code navigation built for AiDX — AST-aware, MCP-native, token-efficient.
Programmable OS-level policy engine for AI agent harnesses — compiles workflow rules into eBPF information-flow policies with corrective feedback.
Function and module-level procedural macro attributes to instrument functions with tracing
Core functionality for crustrace - procedural macro implementation for function tracing
Machine-wide hybrid code search service: BM25 + vector + KG, zero cold-start, MCP server
Simple, composalbe call chains
A command line tool that makes it easy to chain mvn2 calls. Register your dependencies with the "mvn2chain dep" commands and run them with the "mvn2chain exec" command. See "mvn2chain help", "mvn2chain help dep", and "mvn2chain help exec" for more information. Some commands have aliases.
Trace the whole chain of method calls.
Utility that builds callable objects out of a chain of method calls
Allows you to create an object that captures any chain of methods called on it and then displays them when turned into a string.
Use Java-style property notation to execute method call chains on an object.
Enables you to chain calls without explicitly checking nils or exceptions
RunThisAsync allows you to call any chain of methods on a class (or object) asynchronously inside a sidekiq job.
FilterRename is a bulk renaming tool, based on the concept of filters as small operations to perform over sections of the full filename logically represented in targets.
An object on which you can call anything, where nothing happens, but the whole method chain is recorded
# 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
FunctionChain objectifies of the method chain. chain objects can call later or add chain or insert chain or delete chain. supported chain type is following: foo.bar.baz, baz(bar(foo(value))).
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.