dcdpr / jp / 25391613317 / 1
65%
main: 65%

DEFAULT BRANCH: main
Ran
Files 297
Run time 17s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 64.354% (-0.08%) from 64.43%
25391613317.1

push

github

web-flow 
feat(config, conversation, cli): Add `user.name` attribution to turns (#598)

Introduces end-to-end per-turn attribution for the human side of a
conversation. Three layers are added in a single slice:

*Data model.** `jp_config` gains a new `user` module with `UserConfig`
and its `PartialUserConfig` counterpart, wired with the full schematic
boilerplate (assign, delta, fill, to_partial). The single field,
`user.name: Option<String>`, is exposed in `AppConfig` as a nested
setting and round-trips cleanly through serialization.

**Event schema.** `ChatRequest` in `jp_conversation` gains an `author:
Option<String>` field, serialized with `skip_serializing_if = "None"` so
existing persisted conversations deserialize without error. Both
`From<String>` and `From<&str>` impls default it to `None`.

**CLI wiring.** `jp init` now prompts "Your name for conversations:"
during workspace setup. The prompt is pre-filled by cascading through
`git config user.name` then `$USER`/`$USERNAME`. The answer is written
to user-global config so the setting is shared across all workspaces.
The prompt is silently skipped when the name is already configured
globally, or when no global config directory can be determined. On every
`jp query` invocation, the configured name is stamped onto the outgoing
`ChatRequest` as `author`, so transcripts attribute each turn correctly
even when teammates with different local configs continue the same
conversation.

---------

Signed-off-by: Jean Mertz <git@jeanmertz.com>

24641 of 38290 relevant lines covered (64.35%)

177.11 hits per line

Source Files on job 25391613317.1