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

DEFAULT BRANCH: main
Ran
Files 294
Run time 7s
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.655% (+0.3%) from 64.342%
25150333329.1

push

github

web-flow 
feat(attachment_internal, cli): Add `jp://` attachment handler (#590)

Introduces the `jp_attachment_internal` crate, which resolves `jp://`
URIs into text attachments. Today only conversations are supported
(`jp-c...`).

A conversation attachment renders to markdown by default — turn headers,
role sections, tool call pairs — with a selector DSL controlling which
turns and content kinds to include:

```
--attach jp-c17013123456                   # last assistant response
--attach "jp-c17013123456?select=u,a:-1"   # last turn, both sides
--attach "jp-c17013123456?select=*:.."     # entire conversation
--attach "jp-c17013123456?raw"             # selected events as JSON
--attach "jp-c17013123456?raw=all"         # events + config + metadata
```

The CLI parser (`--attach`) now accepts a bare JP ID as shorthand. A
suffix after `?` that isn't a known parameter name (`select`, `raw`) is
automatically promoted to `select=`:

```
jp-c17013123456                  → jp://jp-c17013123456
jp-c17013123456?a:-1             → jp://jp-c17013123456?select=a:-1
jp-c17013123456?select=a:-1      → jp://jp-c17013123456?select=a:-1
jp-c17013123456?raw=all          → jp://jp-c17013123456?raw=all
```

A file path that happens to start with `jp-` but contains non-ID
characters (dots, slashes, uppercase) is left untouched and interpreted
as a regular path. Prepend `./` to force path interpretation if needed.

---------

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

23982 of 37092 relevant lines covered (64.66%)

183.35 hits per line

Source Files on job 25150333329.1