LinkDirectoryAccount
in package
implements
JsonSerializable
`POST /api/v1/tenants/{tenant_id}/directory/links` body.
Table of Contents
Interfaces
- JsonSerializable
Properties
- $userId : string
Methods
- __construct() : mixed
- Constructs a LinkDirectoryAccount.
- fromArray() : self
- Rebuilds a LinkDirectoryAccount from one decoded JSON object.
- jsonSerialize() : array<string, mixed>
- Renders this object for `json_encode()`.
- toArray() : array<string, mixed>
- Renders this object back to its wire form.
Properties
$userId read-only
public
string
$userId
Methods
__construct()
Constructs a LinkDirectoryAccount.
public
__construct(string $userId) : mixed
Parameters
- $userId : string
-
The local account to link. The directory entry is found by the directory, from the account's own username; the caller names no entry.
fromArray()
Rebuilds a LinkDirectoryAccount from one decoded JSON object.
public
static fromArray(array<string, mixed> $data) : self
Parameters
- $data : array<string, mixed>
-
The raw wire object.
Return values
selfjsonSerialize()
Renders this object for `json_encode()`.
public
jsonSerialize() : array<string, mixed>
Any Sensitive it carries stays WRAPPED here, so a log line or a
json_encode($model) in application code prints [SENSITIVE]. The one place a secret
is revealed is ManagementTransport, on the way to the wire
and nowhere else (§27.5).
Return values
array<string, mixed>toArray()
Renders this object back to its wire form.
public
toArray() : array<string, mixed>
§27.4 rule 5: a null property is OMITTED, not emitted as null. On a sparse update those two say opposite things — "leave this alone" versus "set this to nothing" — and only omission means the first.