15
The visibility of the available override methods in Visual Studio Code should be improved.
A good example is the new method ToBase64() of the "Base64 Convert" codeunit.
This function exists with a parameter based on Text and a parameter based on an Instream.
However, when you enter base64cu. in Visual Studio Code (al) and then use Intellisense (Ctrl+Space) to view the available properties and methods, then the Intellisense only shows the following details for the ToBase64 method:
ToBase64(String: Text): Text.
The override method for ToBase64 that accepts instream as a parameter is not shown at all.
The only way to find out that this method has alternative parameters is to select this method in al code first.
You cannot expect us to randomly select methods to see if that function has alternative parameters.
So I believe it's required that all available override methods are shown in the intellisense in Visual Studio Code.
A good example is the new method ToBase64() of the "Base64 Convert" codeunit.
This function exists with a parameter based on Text and a parameter based on an Instream.
However, when you enter base64cu. in Visual Studio Code (al) and then use Intellisense (Ctrl+Space) to view the available properties and methods, then the Intellisense only shows the following details for the ToBase64 method:
ToBase64(String: Text): Text.
The override method for ToBase64 that accepts instream as a parameter is not shown at all.
The only way to find out that this method has alternative parameters is to select this method in al code first.
You cannot expect us to randomly select methods to see if that function has alternative parameters.
So I believe it's required that all available override methods are shown in the intellisense in Visual Studio Code.
STATUS DETAILS
Completed
Business Central Team (administrator)
Business Central Team