Josh Stein

will this PR make it possible to generate the spec json file on releases? to be stored as artifacts on the release as suggested in https://github.com/celestiaorg/celestia-node/issues/2611?

>  it looks like this just outputs the version info? but not the actual api specs? am i missing something here?

**flagging that I do not think this PR should be merged**. it (1) makes it impossible to generate rpc docs, which is counterproductive (2) introduces `celestia docgen` which outputs the...

has this been tested?

> will this PR make it possible to generate the spec json file on releases? to be stored as artifacts on the release as suggested in https://github.com/celestiaorg/celestia-node/issues/2611? thank you, and...

it works for me. but why do we need 2 commands to generate the spec? shouldn't `celestia docgen` handle this for us? also, [in the output I get when testing...

I understand that. I'm trying to understand if it helps accomplish that goal, or of it is going to add more work, that is all

my only feedback would be that the `celestia docgen` command is a little misleading, as it doesn't actually generate the docs. the command to do that is `make openrpc-gen` which...

I still do not think an empty value should return an error, as it is not an error. There is just no share at that namespace and that height.

So @SuperFluffy in this case, at _least_ `foo`'s blob should be returned, and it appears that no blob for `bar` results in an error when querying `[foo, bar]`?