rscalendar 0.1.2

Manage your Google Calendar
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67

# Configuration

rscalendar supports an optional TOML config file for setting defaults.

## File Location

```
~/.config/rscalendar/config.toml
```

The config file is optional. If missing, built-in defaults are used. All config values can be overridden by CLI flags.

## Options

| Key | Type | Default | Description |
|-----|------|---------|-------------|
| `calendar_name` | string | (none) | Default calendar name for all commands |
| `no_browser` | boolean | `false` | Don't open browser during `auth` |

## The `[check]` Section

The `[check]` section defines required properties per event type. It is used by the `rscalendar check` command to validate that events have all expected properties.

```toml
[check]
teaching = ["client", "company", "course"]
working = ["client", "company"]
call = ["client", "company"]
meeting = ["client", "company"]
```

Each key is a `type` property value; its array lists the property keys that must be present on events of that type.

## Example

```toml
# Use a specific calendar by default
calendar_name = "Teaching"

# Always print URL instead of opening browser (headless machines)
no_browser = true

# Required properties per event type
[check]
teaching = ["client", "company", "course"]
working = ["client", "company"]
```

## Precedence

CLI flags always win over config file values:

```bash
# Uses calendar_name from config.toml
rscalendar list

# Overrides config.toml with the flag value
rscalendar list --calendar-name "Work"
```

## Files Overview

| File | Purpose |
|------|---------|
| `~/.config/rscalendar/config.toml` | User preferences |
| `~/.config/rscalendar/credentials.json` | OAuth2 client credentials |
| `~/.config/rscalendar/token_cache.json` | Cached access/refresh tokens |