docsonnet

docsonnet copied to clipboard

Update embedded jsonnet code.

5

Testing using the docker master image, but I believe the pkger.go code is using old jsonnet files that don't have the "filename" and "version" parameters in the d.pkg() function. Given...

Akhalaka

Confusing output for keys with periods in them

1

Both docsonnet documentation fields below are rendered similarly such that I imagine a user could easily be confused by the structure of the data when seeing the Markdown documentation for...

jdbaldry

Attempt to fix #16 in doc-util rendering, this is a bit more complex than I anticipated, I've used this example to test various places where dotted keys can be. ```jsonnet...

Duologic

feat(comments): parser

7

Introduces a comment parser that extracts docsonnet data from specially formed comments, by leveraging as much of Jsonnet as possible: - Comments are extracted from the snippet using Go code...

tombrk

Hi, Would you be able to confirm whether this is expected to work? I find that any object/function under `new()` does not get picked up by `docsonnet` , i.e. there's...

nabadger

tombrk

feat: support collapsible `example` blocks

2

Similar to this: https://golang.org/pkg/encoding/json/#HTMLEscape ### Example Example Example ```jsonnet this is an example ```

ghostsquad

This is an issue to talk about the issues involved in a desugared implementation. AFAIK, the main issue is about the AST not providing access to comments?

ghostsquad

feat: use backticks to emphasize names

8

current: ### fn container.array ``` ### fn container.array ``` suggested: ### fn `container.array` ``` ### fn `container.array` ```

ghostsquad

feat: python documentation-like output

3

I think it would be helpful to allow each parameter, and return value to be explained. Additionally, whether or not an error or assertion could be raised (outside of the...

ghostsquad