Justen Stall
Justen Stall
Is this still on the radar?
Workaround for this is to generate each version to its own file, so markdown links are versioned even though the headers do not reference the version. ```sh crd-ref-docs --source-path=path/to/v1alpha1 --config=apidocs.yaml...
> However it is a bit more complicated. The data in the API allows many Homebrew commands to work offline and significantly faster, such as brew deps, brew info (--json),...
Sure, this is what I would like to do. I want to write this source: Example moved to ticket description.
> Be great to also do object @ripienaar Are you referring to `jetstream.ObjectResult` or `jetstream.ObjectInfo`? [`jetstream.ObjectInfo`](https://github.com/nats-io/nats.go/blob/1949406fa68390b46b1963f0f4a04ec972c5152d/jetstream/object.go#L386) is already covered by its JSON struct tags.
It would be nice to expose the functionality for external implementations of the interfaces so they can use the standard JSON representation. Thoughts on exposing this as a `KeyValueEntryInfo` struct...