Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging framework - chapter outline #56

Merged
merged 4 commits into from
Apr 21, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
92 changes: 92 additions & 0 deletions logger/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,92 @@
# Logging Library

This chapter goes through the building of a simple logging library with the following capabilities:

- Log level filtering
- Multiple channels (stderr, append to file)
- JSON encoding
- Ability to use multiple logging configurations in the same program
- Logger configuration through environment vars

## Chapter structure

The chapter follows a _challenge and response_ pattern. The first iteration builds the simplest logger imaginable (just write to stdout) and each iteration improves on the previous one. After each implementation, its downsides are commented, and the next set of improvements are outlined.

After the final implementation, a recap of the iterations, and the concepts that were explained in each of them, is offered.

_NOTE: On each of the iterations below, I'll list some concepts that could be explained using the iteration code._

_The list is offered as a suggestion: whether we actually flesh out those concepts in this chapter or not will depend on the editorial decisions on chapter ordering and interdependence._

### 0. Minimum viable logger

An extremely simple, single-function "logger" that takes simple arguments (A message and a value) and outputs to Stdout.

This iteration is only pertinent if the chapter introduces the concept of platform. It may be overkill in terms of paring down the first iteration.

``` roc
main =
log "This is a value:" 42
log = \msg, val ->
Stdout.line "$(msg): $(Inspect.toStr val)"
```

_Concepts_:

- Capabilities defined by platform
- Importing from platform

### 1. Append to file

At the end of this iteration, the logger:

- Is composed by just a couple of functions in the main file (no library)
- Appends to a file
- Includes timestamps
- Has a hardcoded output path
- Needs the log file to be created manually

The idea behind its simplicity is to have the least amount of moving parts possible, so we can explore tasks, error handling, and the syntax around them in detail, without the burden of a larger program.

I would like to present the code for this iteration with / without syntax sugar, and take steps to guide the reader to make the connection between type annotations in the documentation, the function calls without syntactic sugar, and the code with sugar.


_Concepts_:

- Task
- Error handling
- Using Inspect
- Backpassing syntax
- Pipe syntax (first pass, simplest case, `f |> a`)
- Reading type annotations

### 2. A usable library

This iteration is a small step from the previous one in terms of complexity of the logger. It mostly expands on the previous one as a reinforcement.

An important step is that the logger becomes a module, and a more realistic use case is presented.

At the end of this iteration, the logger:

- Becomes a module
- Handles log file creation
- Handles permission errors
- Takes a configuration record as argument (which makes it possible to have multiple channels)
- Reads configuration overrides from environment variables

_Concepts_:

- Modules
- Types (configuration record)

### 3. Log level

This iteration adds JSON encoding and log level configuration.

_NOTE_: JSON encoding would depend on [roc-json](https://github.com/lukewilliamboswell/roc-json). If the library is too much, we can do something like rudimentary CSV without escaping or headers: just join a list with commas.

_Concepts_:

- Tags and payloads
- Pattern matching
11 changes: 11 additions & 0 deletions logger/iterations/0-minimal-logger/main.roc
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
app "log-minimal" packages {
cli: "https://github.com/roc-lang/basic-cli/releases/download/0.8.1/x8URkvfyi9I0QhmVG98roKBUs_AZRkLFwFJVJ3942YA.tar.br"
}
imports [cli.Stdout]
provides [ main ] to cli

main =
log "This is a value:" 42

log = \msg, val ->
Stdout.line "$(msg): $(Inspect.toStr val)"
34 changes: 34 additions & 0 deletions logger/iterations/1-append-to-file/main.roc
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
app "log-append" packages {
cli: "https://github.com/roc-lang/basic-cli/releases/download/0.8.1/x8URkvfyi9I0QhmVG98roKBUs_AZRkLFwFJVJ3942YA.tar.br"
}
imports [
cli.Stdout,
cli.File,
cli.Task,
cli.Path,
cli.Utc,
]
provides [ main ] to cli

log = \msg, val ->
path = Path.fromStr "logFile"
Task.await Utc.now \now ->
millis = Utc.toMillisSinceEpoch now
seconds = Num.round (Num.toFrac millis / Num.toFrac 1000)
time = Num.toStr seconds
appendToFile path "$(time) $(msg): $(Inspect.toStr val)\n"

# TODO: figure out type annotation, and its pertinence for this iteration
# appendToFile : Path, Str -> Task {} [FileReadErr Path.Path InternalFile.ReadErr, FileWriteErr Path.Path InternalFile.WriteErr]
appendToFile = \path, msg ->
newBytes = Str.toUtf8 msg
Task.await (File.readBytes path) \existingBytes ->
File.writeBytes path (List.concat newBytes existingBytes)

main =
Task.onErr
(log "This is a value:" 42)
handleErr

handleErr = \err ->
Stdout.line "We found an error: $(Inspect.toStr err)"
35 changes: 35 additions & 0 deletions logger/iterations/1-append-to-file/main.sweet.roc
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
app "log-append" packages {
cli: "https://github.com/roc-lang/basic-cli/releases/download/0.8.1/x8URkvfyi9I0QhmVG98roKBUs_AZRkLFwFJVJ3942YA.tar.br"
}
imports [
cli.Stdout,
cli.File,
cli.Task,
cli.Path,
cli.Utc,
]
provides [ main ] to cli

log = \msg, val ->
path = Path.fromStr "logFile"
now <- Utc.now |> Task.await
millis = Utc.toMillisSinceEpoch now
seconds = Num.round (Num.toFrac millis / Num.toFrac 1000)
time = Num.toStr seconds
appendToFile path "$(time) $(msg): $(Inspect.toStr val)\n"

# TODO: figure out type annotation, and its pertinence for this iteration
# appendToFile : Path, Str -> Task {} [FileReadErr Path.Path InternalFile.ReadErr, FileWriteErr Path.Path InternalFile.WriteErr]
appendToFile = \path, msg ->
newBytes = Str.toUtf8 msg
existingBytes <- File.readBytes path |> Task.await
File.writeBytes path (List.concat newBytes existingBytes)

main =
log "This is a value:"
Task.onErr
(log "This is a value:" 42)
handleErr

handleErr = \err ->
Stdout.line "We found an error: $(Inspect.toStr err)"