Rubberduck - WriteOnlyProperty

Inspection type: CodeQualityIssues

Default severity: Suggestion

Reasoning

Write-only properties are suspicious: if the client code is able to set a property, it should be allowed to read that property as well. Class design guidelines and best practices generally recommend against write-only properties

Quick-Fixes

The following quick-fixes are available for this inspection:

IgnoreOnce: Adds an '@Ignore annotation to ignore a specific inspection result. Applicable to all inspections whose results can be annotated in a module.
IgnoreInModule: Adds an '@IgnoreModule annotation to ignore a inspection results for a specific inspection inside a whole module. Applicable to all inspections whose results can be annotated in a module.
IntroduceGetAccessor: Introduces a 'Property Get' member to make a write-only property read/write; Rubberduck will not infer the property's backing field, the body of the new member must be implemented manually.

Examples

Each example is a self-contained MCVE showing the feature in a single specific scenario.

Standard Module

Named Module1 by default, these are general-purpose standard procedural modules.

Class Module

Named Class1 by default, these modules define the default interface for an object of that type.

Predeclared Class

A class module with its VB_PredeclaredId attribute set to True (with or without a @PredeclaredId annotation).

Interface Module

Abstract interfaces are class modules (with or without an @Interface annotation) whose default interface is not a class type intended to be instantiated.

UserForm Module

A predeclared class with a design-time visual designer using the MSForms UI framework.

Document Module

Owned by the host application, these class modules belong to the host document and may handle various events fired by the host application.