omp-worklog 0.14.5 → 0.14.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: e13d4863a853283acc2fbefdd433c6fa6dd38e5180f483fe647a29067621dfab
4
- data.tar.gz: bdb0edda46245581f6ee7e68c71f3bac263eb6f78996f8dd3ccca7d135985f2a
3
+ metadata.gz: 0ee816df2ce095811beb7021f32892defbbf488840f02f0ff6e3019897f5298c
4
+ data.tar.gz: 443a96a73fa7bd0f4d4c37089712e1fe7126f5bc6d2800be843bf727b816667b
5
5
  SHA512:
6
- metadata.gz: e74327cb9ef7e26c41f34bbc4ffa59d6727373694885a527202d87b0bb2ed2bb36b09767f19d1069856a64770508d91d0430239a9fd9d3568e0ad2f875bdd62c
7
- data.tar.gz: f1b50e45029fc37e59801742120a24608f413c2f78f7ae63a6526774692a6038f4479a05be2514a09165444e480bea34a1d31aa5e1e4f189b10ebab0faade03b
6
+ metadata.gz: 2f54d4a599a17e35d500617c0aa7f44fa591f9167861343a414b3d650266b0c0e843dcdc4f84009f81c9939260b26bef867e00d43fd743418518895c7d7fd83c
7
+ data.tar.gz: 4a89084e3d29bc60fac8eaf06da3c409ec0b165fefc316f5d65777864f61cb2c0fbe55f33829589679d5a7608b74c087a27f89c56db39c725c0782569d4d1bc2
data/README.md CHANGED
@@ -81,7 +81,7 @@ Type `/worklog ` in OMP to discover `timesheet`; date aliases appear after selec
81
81
 
82
82
  ## OMP settings
83
83
 
84
- The manifest declares the following settings. **Persisted settings are currently inactive in the extension**: OMP does not expose resolved user-plus-project plugin settings at factory initialization. Explicit factory options work for programmatic callers and tests. [Issue #134](https://github.com/klondikemarlen/omp-worklog/issues/134) tracks the host dependency; do not assume a successful `omp plugin config set` changed runtime behavior.
84
+ Worklog resolves persisted user settings and project overrides through the supported `omp plugin config list omp-worklog --json` command at initialization, using the OMP project cwd. Project values override user values; explicit factory options override both for programmatic callers and tests. Resolution runs once before commands and tools register; restart or reload the extension after changing settings. A resolution failure reports a diagnostic instead of silently using the wrong destination.
85
85
 
86
86
  - `defaultHours`: hours per business day when a time-off tool call omits `hours`; defaults to `7`.
87
87
  - `holidayRegions`: comma-separated Holidays regions; defaults to `ca_yt`.
@@ -121,6 +121,11 @@ Version `0.14.0` is a clean identity cutover. Uninstall the retired `harvest-wor
121
121
 
122
122
  Version `0.14.3` renames the OMP slash command from `/omp-worklog` to `/worklog`; the `omp-worklog` package identity and CLI executable are unchanged.
123
123
 
124
+ ## Changes in 0.14.6
125
+
126
+ - Activate persisted settings through the supported host CLI before registering commands, completion, and tools.
127
+ - Honor project override precedence and retain explicit factory-option overrides without parsing host configuration files.
128
+
124
129
  ## Changes in 0.14.5
125
130
 
126
131
  - Preserve saved user settings across the required clean plugin reinstall, without copying project overrides or manifest defaults into user configuration.
@@ -155,4 +160,4 @@ omp-worklog --help
155
160
 
156
161
  The release wrapper exports explicit user settings through OMP's configuration CLI from an isolated temporary directory before uninstalling. It saves `settings.json` in an owner-only recovery directory, prints that path without values, restores settings through the CLI, and verifies equality after installation. Project overrides remain project-scoped; unset defaults stay unset. Keep the reported backup until the release is confirmed. If installation or restoration fails, recover from that private snapshot after resolving the reported phase; do not paste its contents into an issue.
157
162
 
158
- After installation, start a new OMP process and exercise `/worklog` completion and a timesheet against synthetic local evidence. Verify that a newly committed SQLite project appears without restarting that process. Existing sessions retain startup-loaded extension code and cannot prove the released artifact. Use explicit factory options for a mapped smoke until #134 is resolved; do not claim persisted-setting activation from that smoke.
163
+ After installation, start a new OMP process and exercise `/worklog` completion and a timesheet against synthetic local evidence. Verify that a newly committed SQLite project appears without restarting that process. Existing sessions retain startup-loaded extension code and cannot prove the released artifact. Verify a persisted user mapping and then a different project override; an explicit factory-option smoke alone does not prove saved configuration activation.
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module OmpWorklog
4
- VERSION = "0.14.5"
4
+ VERSION = "0.14.6"
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: omp-worklog
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.14.5
4
+ version: 0.14.6
5
5
  platform: ruby
6
6
  authors:
7
7
  - Marlen Brunner