Skip to content

BSL212 - Missed a required method parameter

← All rules

Summary

Missed a required method parameter

Identifiers

Field Value
Rule code BSL212
Compatible alias MissedRequiredParameter
Severity ERROR
Without configuration Yes
BSLLS JSON, ON mode without overrides Yes
Registry flag implemented Yes
Tags correctness

The implemented flag describes the registry; it does not certify verified BSLLS parity.

Behavior

  • The public identifier BSL212 and alias MissedRequiredParameter are 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.

[tool.onec-hbk-bsl]
select = ["BSL212"]
ignore = ["MissedRequiredParameter"]

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:
Value = "example";  // noqa: BSL212
  • bsl-disable:
Value = "example";  // bsl-disable: BSL212
  • compatible BSLLS form:
Value = "example";  // BSLLS:MissedRequiredParameter-off

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: BSL212
// code without this diagnostic
// noqa-enable: BSL212

// bsl-disable: BSL212
// code without this diagnostic
// bsl-enable: BSL212

// BSLLS:MissedRequiredParameter-off
// code without this diagnostic
// BSLLS:MissedRequiredParameter-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.

Description

A qualified call, including one split across lines, is not bound to a same-named local method using its name alone. Checking that call requires receiver type information; an unresolved call does not inherit parameters from an unrelated local procedure.

Required parameters must not be omitted when calling methods, otherwise the value Undefined will be passed to the parameter, which the method often cannot process. If the value Undefined is valid, then you need to - explicitly pass a value - or make the parameter optional with a default value of Undefined.

Examples

For example

Procedure ChangeFormFieldColor(Form, FiledName, Color)

Incorrect:

ChangeFormFieldColor(,"Result", StyleColors.ArthursShirtColor); // missing first parameter Form
ChangeFormFieldColor(,,); // missing all required parameters

Correct:

ChangeFormFieldColor(ThisObject, "Result", Color); // all required parameters are specified

Sources

Parameters of procedures and functions (RU)