STY: autoformatting

proto/caosdb/acm/v1alpha1/main.proto

@@ -53,8 +53,7 @@ message PagingResponse {
 ///////////////////////////////////////////
 
 // TODO
-message ListKnownPermissionsRequest {
-}
+message ListKnownPermissionsRequest {}
 
 // TODO
 message ListKnownPermissionsResponse {
@@ -74,10 +73,11 @@ message PermissionDescription {
 message PermissionRule {
   // The permission which is being granted oder denied.
   string permission = 1;
-  // Priority permission rules (TRUE) overrule non-priority (FALSE) permission rules.
+  // Priority permission rules (TRUE) overrule non-priority (FALSE) permission
+  // rules.
   bool priority = 2;
-  // True means that the permission is being granted by this rule, false means the
-  // permission is being DENIED!
+  // True means that the permission is being granted by this rule, false means
+  // the permission is being DENIED!
   bool grant = 3;
 }
 
@@ -190,7 +190,6 @@ enum RoleCapabilities {
   ROLE_CAPABILITIES_ASSIGN = 3;
 }
 
-
 ///////////////////////////////////////////
 // USERS
 ///////////////////////////////////////////
@@ -205,19 +204,23 @@ enum UserStatus {
   USER_STATUS_ACTIVE = 2;
 }
 
-// PasswordSetting - it is handy to have this as a separate message b/c otherwise we could not distinguish between empty string and an unspecified password.
+// PasswordSetting - it is handy to have this as a separate message b/c
+// otherwise we could not distinguish between empty string and an unspecified
+// password.
 message PasswordSetting {
   // The password
   string password = 1;
 }
 
-// EmailSetting - it is handy to have this as a separate message b/c otherwise we could not distinguish between empty string and an unspecified email.
+// EmailSetting - it is handy to have this as a separate message b/c otherwise
+// we could not distinguish between empty string and an unspecified email.
 message EmailSetting {
   // The email adress
   string email = 1;
 }
 
-// EntitySetting - it is handy to have this as a separate message b/c otherwise we could not distinguish between empty string and an unspecified entity.
+// EntitySetting - it is handy to have this as a separate message b/c otherwise
+// we could not distinguish between empty string and an unspecified entity.
 message EntitySetting {
   // The entity which represents this user (e.g. a Person or Device Record).
   string entity_id = 1;
@@ -336,7 +339,6 @@ enum UserCapabilities {
   USER_CAPABILITIES_UPDATE_PASSWORD = 2;
 }
 
-
 ///////////////////////////////////////////
 // SERVICE DEFINITION
 ///////////////////////////////////////////

proto/caosdb/entity/v1/main.proto

@@ -710,8 +710,7 @@ message MultiUpdateEntityACLRequest {
 }
 
 // Response of the MultiUpdateEntityACL rpc
-message MultiUpdateEntityACLResponse {
-}
+message MultiUpdateEntityACLResponse {}
 
 // Entity Access Controll List (ACL)
 message EntityACL {
@@ -739,7 +738,10 @@ message EntityPermissionRule {
   repeated EntityPermissionRuleCapability capabilities = 5;
 }
 
-// What (given enough permissions) can be done with an EntityPermissionRule. E.g. globel entity permission rules, which are to be specified in a configuration file cannot be deleted, thus they are missing the ENTITY_PERMISSION_RULE_CAPABILITY_DELETE capability.
+// What (given enough permissions) can be done with an EntityPermissionRule.
+// E.g. globel entity permission rules, which are to be specified in a
+// configuration file cannot be deleted, thus they are missing the
+// ENTITY_PERMISSION_RULE_CAPABILITY_DELETE capability.
 enum EntityPermissionRuleCapability {
   // Unspecified capability.
   ENTITY_PERMISSION_RULE_CAPABILITY_UNSPECIFIED = 0;