Obsolete implicit and explicit use of 'with'

Enabled for Public preview General availability
Admins, makers, or analysts, automatically This feature is released. Aug 1, 2020 This feature is released. Oct 1, 2020

Business value

The use of with, which allows you to work with members using just simple names instead of qualifying these fully, introduces possible uniqueness collisions when multiple extensions contribute to the same objects. To avoid this going forward, we are marking the use of with, be it implicit or explicit (using the with keyword), as warnings. In addition, we are adding quick actions to fix a file, as well as suppress obsolete warnings for now. At some point, we will change this to errors (one year after GA at the earliest), requiring use to be refactored.

Feature details

For a detailed walkthrough of this feature, see the following description: With or without – that is not a question

See also

Deprecating Explicit and Implicit With Statements (docs)