Merge branch 'microsoft:main' into main
This commit is contained in:
commit
e49c2af933
8 changed files with 26 additions and 28 deletions
|
|
@ -71,7 +71,7 @@ Of course it is possible to have a single object as a central place to emit tele
|
||||||
|
|
||||||
## Candidate data for telemetry
|
## Candidate data for telemetry
|
||||||
|
|
||||||
Telemetry must be **actionable** for the customer. Do not emit signals that they cannot act on (knowing about CPU performance counters on the database is useless if the partner cannot scale the database)
|
Telemetry must be **actionable** for the customer. Do not emit signals that they cannot act on (knowing about CPU performance counters on the database is useless if the partner cannot scale the database).
|
||||||
|
|
||||||
Also, note that customers pay for data ingestion. So be mindful to not flood their telemetry resources. Consider to use TelemetryScope::ExtensionPublisher by default and only use TelemetryScope::All in case the customer can also act on the data.
|
Also, note that customers pay for data ingestion. So be mindful to not flood their telemetry resources. Consider to use TelemetryScope::ExtensionPublisher by default and only use TelemetryScope::All in case the customer can also act on the data.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -166,7 +166,7 @@ It is common use to give certain fields a more describing name. Some examples ar
|
||||||
These fields should always be part of the API Page:
|
These fields should always be part of the API Page:
|
||||||
|
|
||||||
* SystemId
|
* SystemId
|
||||||
* This field should be exposed wit the name ```id```
|
* This field should be exposed with the name ```id```
|
||||||
* SystemModifiedAt
|
* SystemModifiedAt
|
||||||
* This field should be exposed with the name ```lastModifiedDateTime```. If you choose a different name, then the webhook functionality will not work properly.
|
* This field should be exposed with the name ```lastModifiedDateTime```. If you choose a different name, then the webhook functionality will not work properly.
|
||||||
|
|
||||||
|
|
@ -179,8 +179,8 @@ layout
|
||||||
{
|
{
|
||||||
repeater(records)
|
repeater(records)
|
||||||
{
|
{
|
||||||
field(id; SystemId) { }
|
field(id; Rec.SystemId) { }
|
||||||
field(lastModifiedDateTime; SystemModifiedAt) { }
|
field(lastModifiedDateTime; Rec.SystemModifiedAt) { }
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
|
||||||
|
|
@ -26,4 +26,3 @@ When `begin` follows `then`, `else`, `do`, it should be on the same line, preced
|
||||||
...
|
...
|
||||||
end;
|
end;
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -52,4 +52,3 @@ if X then begin
|
||||||
end else
|
end else
|
||||||
(not X)
|
(not X)
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -13,7 +13,7 @@ _Created by Microsoft, Described by waldo_
|
||||||
## Bad code
|
## Bad code
|
||||||
|
|
||||||
```al
|
```al
|
||||||
if Atom = '\>' then HasLogicalOperator := true else begin
|
if Atom = '>' then HasLogicalOperator := true else begin
|
||||||
...
|
...
|
||||||
end;
|
end;
|
||||||
```
|
```
|
||||||
|
|
@ -21,7 +21,7 @@ _Created by Microsoft, Described by waldo_
|
||||||
## Good code
|
## Good code
|
||||||
|
|
||||||
```al
|
```al
|
||||||
if Atom = '\>' then
|
if Atom = '>' then
|
||||||
HasLogicalOperator := true
|
HasLogicalOperator := true
|
||||||
else begin
|
else begin
|
||||||
...
|
...
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue