Generate component protobuf interfaces about dojo HOT 7 CLOSED

I believe codegen is the way to go at first. In theory it's possible to use reflection on the server to "type" the API based on the contract ABI, in practice it's 20x the effort. The benefit of the second approach is that users can use the same server binary across projects, which in turns means ryogoku (the dojo as a service project) can more easily create api servers on the fly.

from dojo.

grpc/protobuf is good at that because all fields are optional and devs can add or delete fields from the struct and the parser still parses them.

from dojo.

Is there a way to do event versioning?

One issue we ran into when building Realms is dealing with historical events and contract upgrades. Let's say you want to display combat history on the client. Every combat result is represented by a CombatOutcome event. The problem is we had to update the structure of the event (e.g. unit composition, adding/removing a field, ...) with a lot of the updates to the combat logic. We settled for a pragmatic approach of doing CombatOutcome1, CombatOutcome2, etc. whenever there was an update of the event.

from dojo.

this can be tackled now we have the manifest

from dojo.

@fracek do you want to tackle this?

from dojo.

It's not super clear to me what's going to be typed. I see that entities are exposed through graphql, so maybe that?

from dojo.

closing this as implementation path has changed

from dojo.