Post date: Mar 25, 2021 2:18:34 PM
2.1.6.8
Issues 1663 and 1832 - Added support for dynamic Visualforce components in Apex including code completion, reference navigation, quick documentation (uses the respective component/attribute doc), and parameter info for parameterized component constructors.
All system Visualforce components are rendered into the OST as the Component class in the root namespace with inner classes for each system component namespace and per-namespace inner classes for each system component in that system namespace. As expected, the OST must be regenerated to see the effect of this change.
All local custom Visualforce components (i.e., *.component files) are also properly proxied into Apex. Usages of custom components and their attributes in Apex are linked to the respective component markup files and apex:attribute elements.
Note that there is currently no support for components from installed managed packages or unpackaged components for which no *.component metadata exists in the local project.
Other related fixes and improvements.