Use bindings config to generate RPC wrappers #1571

New issue

Closed

opened 2024-12-19 06:58:43 +00:00 by fyrchik · 3 comments

fyrchik commented

2024-12-19 06:58:43 +00:00

Owner

neo-go compiler can emit bindings config file which is used by generator to provide custom named types.
As an example, we have Subject* and Group* types in the frostfsid contract.
There is a quirk in neo-go which prevented me from making a PR https://github.com/nspcc-dev/neo-go/issues/3768

In this task:

Introduce Subject*, Group* and Namespace* structs in the rpcclient/frostfsid package. This structs should be autogenerated.
tests should reuse these structs instead of custom ones.
frostfs/client package should reuse the parsing code where possible (some types could be made synonyms, others will persist, because of uint64/big.Int mismatch).

neo-go compiler can emit bindings config file which is used by generator to provide custom named types. As an example, we have `Subject*` and `Group*` types in the frostfsid contract. There is a quirk in neo-go which prevented me from making a PR https://github.com/nspcc-dev/neo-go/issues/3768 In this task: 1. Introduce `Subject*`, `Group*` and `Namespace*` structs in the rpcclient/frostfsid package. This structs should be autogenerated. 2. `tests` should reuse these structs instead of custom ones. 3. `frostfs/client` package should reuse the parsing code where possible (some types could be made synonyms, others will persist, because of uint64/big.Int mismatch).