I forgot I never did this in the original generation code. But there is another possible level to "inspect" — command completion. This comes up in the "diff" tool since sometimes it the options for an argument that change, and today that's not viable in the diff.
For example, ":convert from=" - the from has value like "base64", etc, but "byte-array" is new in 7.15 (I think but diff tool don't tell me that)
/console/inspect request=completion path=convert,from
TYPE COMPLETION STYLE OFFSET PREFERENCE SHOW TEXT
completion [ syntax-meta 0 75 no start of command substitution
completion ( syntax-meta 0 75 no start of expression
completion $ syntax-meta 0 75 no substitution
completion " syntax-meta 0 75 no start of quoted string
completion base32 none 0 96 yes
completion base64 none 0 96 yes
completion byte-array none 0 96 yes
completion hex none 0 96 yes
completion raw none 0 96 yes
completion url none 0 96 yes
completion * none 0 -1 no id prefix
Note
style=none & preference=yes seems to be good clues as there the possible values in a schema. (Now :convert is a bad example from a REST POV).
I forgot I never did this in the original generation code. But there is another possible level to "inspect" — command completion. This comes up in the "diff" tool since sometimes it the options for an argument that change, and today that's not viable in the diff.
For example, ":convert from=" - the from has value like "base64", etc, but "byte-array" is new in 7.15 (I think but diff tool don't tell me that)
Today the
inspect.json
looks like:The idea here be that the
from
part have some new variables. Perhaps some new subkey like_completion
: