Make ValueHandler public so it is easier to create custom status item parsers

[natewalck]

This allows external code to easily parse a given statusitem path

[jessepeterson]

Can you tell me how you're planning to use this?

valueHandler is used for the internal parsing of status items to populate the internal StatusReport by way of parseStatusReportValue (for handing off to the storage layers).

You should just be able to implement a custom jsonpath.Handler and attach it to the mux with a path for anything custom.

[natewalck]

Can you tell me how you're planning to use this?

valueHandler is used for the internal parsing of status items to populate the internal StatusReport by way of parseStatusReportValue (for handing off to the storage layers).

You should just be able to implement a custom jsonpath.Handler and attach it to the mux with a path for anything custom.

I was looking at this as inspiration: https://github.com/jessepeterson/kmfddm/blob/main/ddm/status.go#L204-L209

It appears that parseStatusReportValue handles figuring out the values of the items in the rawbytes, so I was hoping to avoid having to write my own parsing for that.

Is parseStatusReportValue specific to one particular status item payload? Will we need a parser for each one?

[jessepeterson]

I was looking at this as inspiration: https://github.com/jessepeterson/kmfddm/blob/main/ddm/status.go#L204-L209

It appears that parseStatusReportValue handles figuring out the values of the items in the rawbytes, so I was hoping to avoid having to write my own parsing for that.

Almost. The raw bytes are already turned into a *fastjson.Value when it gets to the handler. It's up to the handler to handle that however it wants.

Is parseStatusReportValue specific to one particular status item payload? Will we need a parser for each one?

parseStatusReportValue parses things under .StatusItems.management (i.e. all the "informational" data returned from a status report—excepting declarations which use a different handler under a different, lower/embedded path).

To parse anything other than the four built-in paths yes, you have to write your own handler/parser.