REST-API interface is very inconsistent about fuzz-introspector HOT 9 CLOSED

I've adjusted things now in the referenced PR.

This should have an effect in around ~18 hours. There'll be a JSON schema for each API and they will be visible on the API page, in summary changed all - to _ and fixed some typos.

https://github.com/silvergasp/fuzz-introspector-client will have to be changed -- I'll ping here when the updated webapp is live.

from fuzz-introspector.

That sounds awesome, I'd love to follow along, is it public?

Naming and conventions should be standardized, I agree.

I think it may make sense to define something more concrete for the API, e.g. a spec of sort that can be utilized, either via protobuf or similar.

from fuzz-introspector.

So far it's part of a private project. But I'd be happy to spin that component out into an open-source project, if there is interest.

from fuzz-introspector.

@DavidKorczynski Client lib here, need to add some docs and create a crates.io package but you should be able to get an idea how to use it from the examples directory. It is pretty much feature complete in terms of querying the API.

from fuzz-introspector.

Crate docs here are here fuzz-introspector-client.

from fuzz-introspector.

Cool, thanks for the links @silvergasp

I might approach this in a two-step approach: first fix up so naming and conventions are consistent; then come up with some specification which can be used for serialization across languages.

from fuzz-introspector.

Sounds reasonable to me, protobuf/grpc sounds nice.

from fuzz-introspector.

This should be good now @silvergasp !

I think for now we'll stay with JSON shemas to keep things light.

from fuzz-introspector.

One more inconsistency. "src_file" vs "source_file". Would it make sense to fix that too?

from fuzz-introspector.