You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Rename resource fields in request messages that don't follow style guide #1163
I ran the apitool linter (prototype in #1162 ) and I got this:
Validating ateapi.proto (Control), 13 rule(s)...
✓ resource-metadata
✗ list-method-shape
ateapi.Control.ListActorSnapshots: repeated field is named "snapshots", want "actor_snapshots" (the plural resource name, matching the method name)
✓ request-name-matches-method
✓ standard-method-returns-resource
✗ get-request-single-objectref
ateapi.Control.GetActorSnapshot: resource field is named "snapshot", want "actor_snapshot"
ateapi.Control.GetActorSnapshotTag: resource field is named "tag", want "actor_snapshot_tag"
✗ delete-request-shape
ateapi.Control.DeleteActor: field "any_state" is not a message, want ateapi.ObjectRef or ateapi.DeleteOptions - non-resource control fields belong in ateapi.DeleteOptions
ateapi.Control.DeleteActorSnapshotTag: resource field is named "tag", want "actor_snapshot_tag"
✓ list-response-name-matches-method
✓ enum-zero-value-unspecified
✓ enum-values-prefixed
✓ resource-status-field-shape
✓ no-oneofs
✗ create-update-request-embeds-resource
ateapi.Control.UpdateActorSnapshotTag: resource field is named "tag", want "actor_snapshot_tag"
Activity
Fix resource names for ActorSnapshotTag methods. (#1167)
Introduce a `apitool` CLI for the substrate API. (#1162)