JSON Schema => Capability Types #647
Conversation
| @@ -0,0 +1,82 @@ | |||
| { | |||
There was a problem hiding this comment.
Will move it to an actual streams folder in a follow-up. This should be the real deal (today; duplicating for testing purposes as it might change later).
| @@ -0,0 +1,128 @@ | |||
| // Code generated by pkg/capabilities/cli, DO NOT EDIT. | |||
There was a problem hiding this comment.
This is what will be generated for each capability. Will need work to include capability type, maybe figure out the encoded string => []byte conversion, too.
| } | ||
|
|
||
| // UnmarshalJSON implements json.Unmarshaler. | ||
| func (j *StreamsCapabilityOutputsElem) UnmarshalJSON(b []byte) error { |
There was a problem hiding this comment.
I wonder if we could swap this to Proto/Values generation. Also, whether that would be useful.
go.mod
Outdated
| ) | ||
|
|
||
| require ( |
There was a problem hiding this comment.
We don't know why the tooling sometimes creates these extra indirect blocks, but if you combine them, then tidy will sort them for you.
| ) | |
| require ( |
DeividasK
changed the title
|
PR is failing because of failures in downstream dependencies, namely smartcontractkit/chainlink#13820 |
Long-term, we need JSON Schema to generate types for various different capability use cases to be able to interoperate. Currently, I'm creating JSON Schemas by hand for each and then generating the go types.
Long-term, this is probably not the right place for this CLI tool. Will aim to move it to
capabilitiesrepo.Credits:
Heavily inspired by @nolag prototype:
https://github.com/smartcontractkit/ryantinianovscratch/tree/rtinianov_jsonSchemaToBuilder/jsonschematobuilder