| commit | 2ec90c023d7c62a38cfbd2f34f55093ab38ccf85 | [log] [tgz] |
|---|---|---|
| author | Kevin Moore <kevmoo@users.noreply.github.com> | Tue May 28 12:41:43 2024 -0700 |
| committer | GitHub <noreply@github.com> | Tue May 28 12:41:43 2024 -0700 |
| tree | 040e0d87f712b652d5a9d7d90bbbe7bf63c68622 | |
| parent | 2fb4fbff6ee8d26fee1f3576fa0500057d897afd [diff] |
bump lints dep and fix (#92)
Tools for creating a persistent worker loop for bazel.
There are two abstract classes provided by this package, AsyncWorkerLoop and SyncWorkerLoop. These each have a performRequest method which you must implement.
Lets look at a simple example of a SyncWorkerLoop implementation:
import 'dart:io'; import 'package:bazel_worker/bazel_worker.dart'; void main() { // Blocks until it gets an EOF from stdin. SyncSimpleWorker().run(); } class SyncSimpleWorker extends SyncWorkerLoop { /// Must synchronously return a [WorkResponse], since this is a /// [SyncWorkerLoop]. WorkResponse performRequest(WorkRequest request) { File('hello.txt').writeAsStringSync('hello world!'); return WorkResponse()..exitCode = EXIT_CODE_OK; } }
And now the same thing, implemented as an AsyncWorkerLoop:
import 'dart:io'; import 'package:bazel_worker/bazel_worker.dart'; void main() { // Doesn't block, runs tasks async as they are received on stdin. AsyncSimpleWorker().run(); } class AsyncSimpleWorker extends AsyncWorkerLoop { /// Must return a [Future<WorkResponse>], since this is an /// [AsyncWorkerLoop]. Future<WorkResponse> performRequest(WorkRequest request) async { await File('hello.txt').writeAsString('hello world!'); return WorkResponse()..exitCode = EXIT_CODE_OK; } }
As you can see, these are nearly identical, it mostly comes down to the constraints on your package and personal preference which one you choose to implement.
A package:bazel_worker/testing.dart file is also provided, which can greatly assist with writing unit tests for your worker. See the test/worker_loop_test.dart test included in this package for an example of how the helpers can be used.
Please file feature requests and bugs at the issue tracker.