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
Copy file name to clipboardExpand all lines: api_open_fga.go
+6-4Lines changed: 6 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -304,8 +304,9 @@ type OpenFgaApi interface {
304
304
You may also specify `contextual_tuples` that will be treated as regular tuples. Each of these tuples may have an associated `condition`.
305
305
You may also provide a `context` object that will be used to evaluate the conditioned tuples in the system. It is strongly recommended to provide a value for all the input parameters of all the conditions, to ensure that all tuples be evaluated correctly.
306
306
The response will contain the related users in an array in the "users" field of the response. These results may include specific objects, usersets
307
-
or type-bound public access. Each of these types of results is encoded in its own type and not represented as a string.In certain cases of negation via the `but not` operator, some results are marked as excluded from the main set of results. These exclusions
308
-
are returned in the `excluded_users` property and should be handled appropriately at the point of implementation.The number of users in the response array will be limited by the execution timeout specified in the flag OPENFGA_LIST_USERS_DEADLINE and by the upper bound specified in the flag OPENFGA_LIST_USERS_MAX_RESULTS, whichever is hit first.
307
+
or type-bound public access. Each of these types of results is encoded in its own type and not represented as a string.In cases where a type-bound public acces result is returned (e.g. `user:*`), it cannot be inferred that all subjects
308
+
of that type have a relation to the object; it is possible that negations exist and checks should still be queried
309
+
on individual subjects to ensure access to that document.The number of users in the response array will be limited by the execution timeout specified in the flag OPENFGA_LIST_USERS_DEADLINE and by the upper bound specified in the flag OPENFGA_LIST_USERS_MAX_RESULTS, whichever is hit first.
309
310
The returned users will not be sorted, and therefore two identical calls may yield different sets of users.
310
311
* @param ctx _context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background().
311
312
* @param storeId
@@ -2708,8 +2709,9 @@ An `authorization_model_id` may be specified in the body. If it is not specified
2708
2709
You may also specify `contextual_tuples` that will be treated as regular tuples. Each of these tuples may have an associated `condition`.
2709
2710
You may also provide a `context` object that will be used to evaluate the conditioned tuples in the system. It is strongly recommended to provide a value for all the input parameters of all the conditions, to ensure that all tuples be evaluated correctly.
2710
2711
The response will contain the related users in an array in the "users" field of the response. These results may include specific objects, usersets
2711
-
or type-bound public access. Each of these types of results is encoded in its own type and not represented as a string.In certain cases of negation via the `but not` operator, some results are marked as excluded from the main set of results. These exclusions
2712
-
are returned in the `excluded_users` property and should be handled appropriately at the point of implementation.The number of users in the response array will be limited by the execution timeout specified in the flag OPENFGA_LIST_USERS_DEADLINE and by the upper bound specified in the flag OPENFGA_LIST_USERS_MAX_RESULTS, whichever is hit first.
2712
+
or type-bound public access. Each of these types of results is encoded in its own type and not represented as a string.In cases where a type-bound public acces result is returned (e.g. `user:*`), it cannot be inferred that all subjects
2713
+
of that type have a relation to the object; it is possible that negations exist and checks should still be queried
2714
+
on individual subjects to ensure access to that document.The number of users in the response array will be limited by the execution timeout specified in the flag OPENFGA_LIST_USERS_DEADLINE and by the upper bound specified in the flag OPENFGA_LIST_USERS_MAX_RESULTS, whichever is hit first.
2713
2715
The returned users will not be sorted, and therefore two identical calls may yield different sets of users.
2714
2716
- @param ctx _context.Context - for authentication, logging, cancellation, deadlines, tracing, etc. Passed from http.Request or context.Background().
NewListUsersResponse instantiates a new ListUsersResponse object
17
16
This constructor will assign default values to properties that have it defined,
@@ -46,26 +45,6 @@ and a boolean to check if the value has been set.
46
45
SetUsers sets Users field to given value.
47
46
48
47
49
-
### GetExcludedUsers
50
-
51
-
`func (o *ListUsersResponse) GetExcludedUsers() []ObjectOrUserset`
52
-
53
-
GetExcludedUsers returns the ExcludedUsers field if non-nil, zero value otherwise.
54
-
55
-
### GetExcludedUsersOk
56
-
57
-
`func (o *ListUsersResponse) GetExcludedUsersOk() (*[]ObjectOrUserset, bool)`
58
-
59
-
GetExcludedUsersOk returns a tuple with the ExcludedUsers field if it's non-nil, zero value otherwise
60
-
and a boolean to check if the value has been set.
61
-
62
-
### SetExcludedUsers
63
-
64
-
`func (o *ListUsersResponse) SetExcludedUsers(v []ObjectOrUserset)`
65
-
66
-
SetExcludedUsers sets ExcludedUsers field to given value.
67
-
68
-
69
48
70
49
[[Back to Model list]](../README.md#documentation-for-models)[[Back to API list]](../README.md#documentation-for-api-endpoints)[[Back to README]](../README.md)
0 commit comments