Flags MSForms controls being accessed from outside the UserForm that contains them.
New This feature is currently only available in pre-release builds (or the xmldoc asset doesn’t yet exist on main
!).
Inspection type: LanguageOpportunities
Default severity: Hint
MSForms exposes UserForm controls as public fields; accessing these fields outside the UserForm class breaks encapsulation and couples the application logic with specific form controls rather than the data they hold. For a more object-oriented approach and code that can be unit-tested, consider encapsulating the desired values into their own 'model' class, making event handlers in the form manipulate these 'model' properties, then have the code that displayed the form query this encapsulated state as needed
The following quick-fixes are available for this inspection:
Each example is a self-contained MCVE showing the feature in a single specific scenario.
Module1
by default, these are general-purpose standard procedural modules.Class1
by default, these modules define the default interface for an object of that type.VB_PredeclaredId
attribute set to True
(with or without a @PredeclaredId
annotation).@Interface
annotation) whose default interface is not a class type intended to be instantiated.
The content of this page was generated from xml/comments in the source code compiled into Rubberduck.CodeAnalysis.xml
.
Edit this page