BSL178 - Using of deprecated platform 8.3.17 global methods¶
Summary¶
Using of deprecated platform 8.3.17 global methods
Identifiers¶
| Field | Value |
|---|---|
| Rule code | BSL178 |
| Compatible alias | DeprecatedMethods8317 |
| Severity | INFORMATION |
| Without configuration | Yes |
BSLLS JSON, ON mode without overrides |
Yes |
Registry flag implemented |
Yes |
| Tags | deprecated, compatibility |
The implemented flag describes the registry; it does not certify verified BSLLS parity.
Behavior¶
- The public identifier
BSL178and aliasDeprecatedMethods8317are stable. - The rule reports the cases documented on this page.
- Suppressions and project configuration are applied before publication.
- The rule requires neither an external analyzer nor network access.
Configuration and suppression¶
BSL### is the primary stable identifier. The compatible alias is accepted
in select, ignore, and compatible block suppression comments.
All three suppression families support both a current line and a range. When an opening comment follows code, it affects only that line. Use any one form:
noqa:
bsl-disable:
- compatible
BSLLSform:
When the same opening comment is on a line by itself, it starts a range. Close it with the matching marker from the same family:
// noqa: BSL178
// code without this diagnostic
// noqa-enable: BSL178
// bsl-disable: BSL178
// code without this diagnostic
// bsl-enable: BSL178
// BSLLS:DeprecatedMethods8317-off
// code without this diagnostic
// BSLLS:DeprecatedMethods8317-on
To disable the rule until the end of the file, omit the closing
noqa-enable, bsl-enable, or BSLLS:…-on marker.
Opening and closing markers must belong to the same family.
Diagnostic description¶
The rule checks global calls to BriefErrorDescription, DetailErrorDescription,
and ShowErrorInfo, including their Russian aliases КраткоеПредставлениеОшибки,
ПодробноеПредставлениеОшибки, and ПоказатьИнформациюОбОшибке. It highlights
the method name. Object-qualified calls, strings, and comments are skipped.
If Configuration.xml contains CompatibilityMode or
ConfigurationExtensionCompatibilityMode below Version8_3_17, the check is
skipped. It runs for version 8.3.17 or later, and when no compatibility mode is
found.
For example, DetailErrorDescription(ErrorInfo()) is reported when the
compatibility mode allows the check; an object-qualified call is skipped.