mirror of
https://github.com/microsoft/BCQuality.git
synced 2026-08-06 17:36:53 +01:00
62dabf9a11
The /samples/ top-level tree is replaced with sibling files in each
knowledge-layer folder. An article and its demonstrations now live
side-by-side:
microsoft/knowledge/<domain>/<slug>.md
microsoft/knowledge/<domain>/<slug>.good.al
microsoft/knowledge/<domain>/<slug>.bad.al
Rationale:
- Proximity. An article and its paired samples are one unit; the
filesystem now reflects that.
- Layer ownership. Samples inherit layer precedence for free -- a
/custom/ fork can override an article and its samples atomically,
which the shared /samples/ tree previously made awkward.
- Trivial migration path. Action-skill source globs
(*/knowledge/<domain>/**/*.md) are unchanged; sample discovery is a
sibling-filename lookup.
Changes:
- git mv of all 65 sample files from samples/<domain>/<slug>/{bad,good}.al
to microsoft/knowledge/<domain>/<slug>.{bad,good}.al (history preserved).
- Update See-sample references in all 37 articles that ship samples.
- skills/read.md: replace the no-code-blocks bullet with a pointer to a
new Sample files section that fully specifies the sibling convention,
the kinds (good/bad + forward-compatible), multi-technology rules,
demonstration-only status, and layer-precedence behaviour.
- skills/write.md: update the samples pointer to match.
- README.md: annotate the knowledge tree with the sample sibling shape.
- samples/README.md deleted; content lifted into skills/read.md.
- Both generators (C:\temp\gen_performance_knowledge.py,
C:\temp\gen_security_knowledge.py) updated to emit at the new paths
and to stop writing samples/README.md. Re-running them is idempotent
against the committed layout.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
24 lines
602 B
AL
24 lines
602 B
AL
codeunit 50224 "Sec Sample ErrorDisclosure Good"
|
|
{
|
|
var
|
|
ConnectionFailedErr: Label 'Connection to the external service failed. Contact your administrator.';
|
|
|
|
procedure Connect()
|
|
begin
|
|
if not TryConnect() then begin
|
|
LogConnectionFailure(GetLastErrorText());
|
|
Error(ConnectionFailedErr);
|
|
end;
|
|
end;
|
|
|
|
[TryFunction]
|
|
local procedure TryConnect()
|
|
begin
|
|
// ...
|
|
end;
|
|
|
|
local procedure LogConnectionFailure(Detail: Text)
|
|
begin
|
|
// Route to controlled logging (Session.LogMessage, activity log, etc.).
|
|
end;
|
|
}
|