The behavior of unlike-assets is difficult to trace without logging, hence this module.
You should use this module with your own build process to ensure consistent output, especially
when using the CLI.
3.1 Basic Interface
This logger uses the 'unlike-assets topic, has no parent, and subscribes to all levels of detail.
3.2 Building Reports
such that any log messages sent to unlike-logger
are intercepted and forwarded to the printer. Messages are customized using
several parameters. See Display Parameters
Returns the value returned from proc, and a dictionary holding counts
for the number of each event encountered during evaluation of proc.
If no events are captured for a level, the dictionary will still hold the level
as a key with a value of 0.
, except the return values are discarded.
, except only the event counts dictionary is returned.
3.3 Display Parameters
Informs receivers if 'debug events should be displayed to the end user.
If #t, log messages will include ANSI color codes.
If #t, the logger topic "unlike-assets: " will prefix each log message.
If #t, the logger will include all events in end-user output, not just those for the 'unlike-assets topic.
Combined with (show-debug? #t), this can be extremely noisy. Use only if detailed feedback from Racket internals matter for your purposes.
If #t, prefix each log message with the message’s level of detail.
Controls which levels are forwarded to (current-error-port)
be default. Typically you would
change this if you want to (not) count warnings as errors or constrict STDOUT to a single level without
using another process.
A string prefix applied to every message. This is useful in things like multi-threaded
builds where each thread needs to identify itself.
These procedures prepare clear and unclear dependency references for placement in a log message.
The output will be printed in display