solana_kit_functional 0.9.3

Pipe and compose utilities for the Solana Kit Dart SDK.

solana_kit_functional

Warning

This package is deprecated and kept only as a compatibility shim. New code should import the Pipe extension from package:solana_kit_transaction_messages/solana_kit_transaction_messages.dart or the umbrella package:solana_kit/solana_kit.dart instead.

The standalone solana_kit_functional package may be removed in a future release once downstream migration is complete.

The Pipe extension that used to live here now lives in solana_kit_transaction_messages. This package is an empty placeholder that exists so existing imports keep resolving during migration.

Installation

Install the package directly:

dependencies:
  "solana_kit_functional": ^0.9.3

If your app uses several Solana Kit packages together, you can also depend on the umbrella package instead:

dart pub add solana_kit

Inside this monorepo, Dart workspace resolution uses the local package automatically.

Documentation

• Package page: https://pub.dev/packages/solana_kit_functional
• API reference: https://pub.dev/documentation/solana_kit_functional/latest/
• Workspace docs: https://openbudgetfun.github.io/solana_kit/
• Package catalog entry: https://openbudgetfun.github.io/solana_kit/reference/package-catalog#solana_kit_functional
• Source code: https://github.com/openbudgetfun/solana_kit/tree/main/packages/solana_kit_functional

For architecture notes, getting-started guides, and cross-package examples, start with the workspace docs site and then drill down into the package README and API reference.

Usage

Import Pipe from solana_kit_transaction_messages instead:

import 'package:solana_kit_transaction_messages/solana_kit_transaction_messages.dart';

void main() {
  final result = 5.pipe((value) => value * 2 + 1);

  print(result); // 11
}

Example

Use example/main.dart as a runnable starting point for solana_kit_functional.

• Import path: package:solana_kit_functional/solana_kit_functional.dart
• This section is centrally maintained with mdt to keep package guidance aligned.
• After updating shared docs templates, run docs:update from the repo root.

Maintenance

• Validate docs in CI and locally with docs:check.
• Keep examples focused on one workflow and reference package README sections for deeper API details.